Skip to content
This repository was archived by the owner on Jun 24, 2022. It is now read-only.

Commit bfadb44

Browse files
authored
Execution policy fix, unblock-file instructions, other small changes.
Some people reported that they had to modify their execution policy. This is likely to be the case for most people, so I've added a short section on it in case anyone didn't know. Same goes for Unblock-File. Edited a section title to better describe it. Edited MS Teams link title.
1 parent bbc7031 commit bfadb44

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

README.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Sends notifications from Veeam Backup & Restore to Slack
55
![Chat Example](https://raw.githubusercontent.com/tigattack/VeeamSlackNotifications/master/asset/img/screens/sh-2.png)
66

77
---
8-
[MS Teams version.](https://github.com/tigattack/VeeamTeamsNotifications)
8+
[MS Teams fork](https://github.com/tigattack/VeeamTeamsNotifications)
99
---
1010
## [Discord Setup](https://blog.tiga.tech/veeam-b-r-notifications-in-discord/)
1111

@@ -36,7 +36,7 @@ Unzip the archive and make sure the folder is called: `VeeamSlackNotifications`
3636
```powershell
3737
Invoke-WebRequest -Uri https://github.com/tigattack/VeeamSlackNotifications/archive/2.1.zip -OutFile C:\VeeamScripts\VeeamSlackNotifications-v1.0.zip
3838
```
39-
You may recieve an SSL error as winhttp uses TLS1 by default, which GitHub appears to no longer accept. IF you recieve this error, run the following and re-issue the above command.
39+
You may recieve an SSL error as winhttp uses TLS1 by default in some case (depends on a few things), which GitHub appears to no longer accept. IF you recieve this error, run the following and re-issue the above command.
4040
```powershell
4141
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
4242
```
@@ -48,7 +48,7 @@ Ren C:\VeeamScripts\VeeamSlackNotifications-2.2 C:\VeeamScripts\VeeamSlackNotifi
4848
rm C:\VeeamScripts\VeeamSlackNotifications-v2.2.zip
4949
```
5050

51-
#### Configure the project:
51+
#### Prepare for use
5252
Make a new config file
5353
```shell
5454
cp C:\VeeamScripts\VeeamSlackNotifications\config\vsn.example.json C:\VeeamScripts\VeeamSlackNotifications\config\vsn.json
@@ -57,6 +57,16 @@ cp C:\VeeamScripts\VeeamSlackNotifications\config\vsn.example.json C:\VeeamScrip
5757
```shell
5858
notepad.exe C:\VeeamScripts\VeeamSlackNotifications\config\vsn.json
5959
```
60+
Unblock the script files. Windows often blocks execution of downloaded scripts.
61+
```powershell
62+
Unblock-File C:\VeeamScripts\VeeamSlackNotifications\SlackNotificationBootstrap.ps1
63+
Unblock-File C:\VeeamScripts\VeeamSlackNotifications\SlackVeeamAlertSender.ps1
64+
Unblock-File C:\VeeamScripts\VeeamSlackNotifications\Helpers\Helpers.psm1
65+
```
66+
You may also need to set your PowerShell execution policy to Unrestricted if you're still having issues after unblocking the scripts.
67+
```powershell
68+
Set-ExecutionPolicy Unrestricted
69+
```
6070

6171
Finally, open Veeam and configure your jobs. Edit them and click on the <img src="asset/img/screens/sh-3.png" height="20"> button.
6272

0 commit comments

Comments
 (0)