–  Click on Add link in the Actions pane. This will bring up the dialog box. Enter file extensions, specify the corresponding MIME type and click on the OK button.File name extension: .iso
MIME Type : application/octet-stream

–  Restart your IIS Server from the IIS Manager.

The post Upgrade your Windows to latest version of Windows 11 appeared first on SankalpIT - Plugins for Automate.

See screenshot.

• Know MySQLEXE file path. There are few steps you need to follow, in order to know MYSQL setup folder.

Note :

• Know to location of my.ini file. Open the properties of LabMySQL service and look at the path of Path to executable .
• Open the my.ini file in notepad and find “ basedir ” variable.
• Open explorer and navigate to value of basedir variable and then open bin folder.
• There, you can see “mysql.exe” file. Hold shift key and right click on “mysql.exe” file and then click on “Copy as path”.

See screenshot.

• Lastly, you need to know where your database is stored.
• Again, Open my.ini file in notepad and find “ datadir ” variable.
• Value of datadir variable is your ConnectWise Automate database folder path.

The post How to Restore ConnectWise Automate Database appeared first on SankalpIT - Plugins for Automate.

Requirements

• Automate Version 10.5+

Installation Procedure:

Installation of the Plugin:

There is a Link Library known as .dll file. Follow the instructions below to install the .DLL file to your LabTech System.

Installation is simple and is done directly from your workstations or LT servers desktop. You only need to install the .dll one time, have all console users log out and back in to get the updated plugins once installed.

 

You will need to unzip the downloaded package and extract the .dll file to a location you can browse with your desktop system. You must unblock the .dll before trying to install it. To unblock right-click the .dll file and select properties. On the main properties page select the unblock button if one exists.

If not already open, open your LT/Automate control center and navigate up to the [Help] menu where you will find the Plugin Manager.

Now select the Advanced -> Manage Plugins -> Add Plugin menu and browse to the DLL file you extracted and select it.

You will be presented with the plugin registration window, select Save and Close.

Now back on the main screen you will find the Reboot Schedule Plugin for ConnectWise Automate plugin in your list of available plugins but it is not yet activated. Right click on the plugin and select Enable.

Once enabled, If it is not already restarted database service of LabTech/Automate server, we can reload the Database Agent service from plugin manager. See following screenshot.

Now, a prompt will show up asking you to restart the database agent. Enter YES.

Then, the database agent will restart.

Now reload the Automate Control center, this will load the new plugin on the relaunch and you are all ready to get started.

To check if the Reboot Schedule Plugin is working fine, just verify that in the Plugin Manager->Enabled Plugins, the [DBLoaded] and [IIS Loaded] columns are green check marks.

How to Configure Reboot Schedule on Group:

Group Screen: This is a screen where you can make a schedule to reboot the machines by your choice. You can use multiple schedules for one group. There is an option to save Notes.

1.  Check the checkbox called “Enable Reboot Schedule” to make sure that you want to make a schedule.

2.  Disable timezone compensation: If this checkbox is checked that means you want to reboot machines according to LabTech server’s timezone.

3.  Reboot Schedule for Today Only: Go with this procedure if you would like to reboot machines in current day. Like if you would like to reboot the machine at your night time you can use this schedule. Once the specified schedule is gone, the procedure will get disabled automatically.

4.  Reboot Schedule on Weekly Basis: Select this procedure if you want to reboot machines on a weekly basis. You will have to choose

Week(s) of the month,
Day(s) of the week,
And finally, time to reboot.

5.  Reboot Schedule on Date of this Month: Choose this option if you would like to reboot the machines on date of each month.

6.  Reboot Schedule on Day(s) of Month: Choose this procedure if you would like to reboot your machines at a specific day(s) of each month.

7.  Reboot Schedule on Last day of Month: Choose this procedure if you would like to reboot your machines on the last day of each month.

To view Reboot Schedule and History of reboots:

LABTECH 10.5, 11
Click on View->Reboot Schedule Overview.

LabTech 12:
Tool-> Reboot Schedule Overview

• Schedule Tab: you will have information about all schedules that you have configured using the reboot schedule tab on groups.
• History Tab: You can view all the history of reboots.

The post Reboot Schedule Plugin for ConnectWise Automate appeared first on SankalpIT - Plugins for Automate.

Configure Incoming Webhook for a channel.

1. Open MS Teams, select “Channel,” and then click on More options (…) and choose Connectors.

2. A pop-up window will come up. Select All from the Category section in the left pane, find Incoming Webhook, and click Add button to add Incoming Webhook.

3. Another window will pop up. Click on the Install button.

Branding the connector and copying the URL.

1. After configuring the Incoming Webhooks connector, we now need to brand it.
2. Give it a Name, and you may change the image (Optional) and click on Create button.

3. Final step is to copy the URL and click on the Done button.

Note: This URL, we will provide in

Connectwise Automate →

System →

Users & Contacts →

System Contacts

. Create a Contact named Default


Sendto MSTeams

. Open it and click on

Sendto MSTeams →

Incoming Webhook field.

How do I get URLs for already configured Incoming Webhooks?

If you forget to copy the URL of Incoming Webhooks of a Channel, you get it by following the simple steps given below.

a. Select Channel and click the more options (…) button.
b. Click on connectors.
c. Following window will pop up.
d. By Default, All Category (Left Pane) is selected. Make sure you select the Configured link (highlighted in yellow) from the Left pane.

e. Now, the window on the right pane has refreshed and shown only the configured connectors.
f. Under Incoming Webhook, click on the Configured link and select Manage. There you can copy the URL for your existing connector(s). see screenshot.

The post How to get incoming webhook URL of a channel of MS Teams? appeared first on SankalpIT - Plugins for Automate.

How do I get Slack Incoming webhook URL?

You just need to walk through a quick 3-step process to get your job done.

• Create a Slack app.
• Enable Incoming Webhooks
• Create an Incoming Webhook.

Create a Slack app.

• Navigate to this URL: https://api.slack.com/apps?new_app=1
• Login to your Slack account if you see, “You’ll need to sign in to your Slack account to create an application.”
• Then, it will prompt a window to Create a Slack App.
• In-App Name field: Give your application a meaningful name.
• In Development Slack Workspace field, select your slack workspace.
• Click Create App button.

Enable Incoming Webhooks

After creating, you’ll be redirected to the settings page for your new app (if you are using an existing app, just load its settings via the Your Apps page).

• Select Incoming Webhooks feature (highlighted in yellow).

• And then, click the Activate Incoming Webhooks toggle to switch it on.

Create an Incoming Webhook.

Now that Incoming Webhooks is enabled, the settings page should refresh, and some extra options will appear. In this section, you will authorize your app to send messages to a slack channel that will be selected in the following section.

• Scroll down and Click on Add New Webhook to Workspace button. On the next page, you need to select a channel on which Sendto Slack plugin will send messages.

• In Post to section, select the channel and click Authorize button.

You’ll be sent back to your app settings, and you should now see a new entry under the Webhook URLs for Your Workspace section, with a Webhook URL that’ll look something like this:

https://hooks.slack.com/services/XXXXXXXXXX/XXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXX

That URL is your shiny new Incoming Webhook.

Your app setting page should like look this one:

• Copy Webhook URL by clicking on the Copy button (marked in yellow). That’s it.

The post How to Create Slack Incoming Webhook URL appeared first on SankalpIT - Plugins for Automate.

Technical Documentation

Sendto Slack plugin requirements.

• License key from SankalpIT
• Sendto Slack DLL file – Download Now!
• CW Automate 12 or higher versions.
• Incoming webhook URL. Click here to know more.
• Default Contact for this plugin in CW Automate.

What will change in CW Automate after Sendto Slack plugin installation?

Sendto Slack plugin installation is very straight forward process. Click here to know more about it.

Once you done with installation, you can check what has changed or added to your system by following the steps given below:

• It creates a new tab called ‘Sendto Slack‘ on the Dashboard. You may check by navigating System-> Configuration ->Dashboard -> Config -> Integration tab. An MSP should should the Incoming Webhooks URL for Default Slack Channel for his team on this screen.
• It also creates a new tab on the Contact Screen. There you may provide Incoming Webhook URL of any Slack channel or user to whom you want to send an alert using Alert Template.
• Add new Alert Action in Alert Template that is called Sendto Slack.

Using Sendto Slack – Activate your plugin license.

1. Navigate to System -> Configuration ->Dashboard -> Config -> Integration -> Sendto Slack tab.
2. Enter your license key in the License Key field.
3. Click Validate License link. It will show as active after activation.

Using Sendto Slack in Production.

Incoming Webhooks URL of the Slack Channel of the MSP Workspace.
Provide your Incoming Webhooks URL in Dashboard.

1. Navigate to System -> Configuration ->Dashboard -> Config -> Integration -> Sendto Slack.
2. Enter your Incoming Webhooks URL where it labeled as Incoming Webhooks:

1. Then click Test Link to test your Incoming Webhooks. If you get the message in the slack channel, it means everything is working perfectly.

Create Default Contact for Sendto Slack.
In this section, we will create Default Contact that will be used by plugin’s Default Alert Template in the upcoming section.
Let’s Create Default Contact for the plugin.

• Create a new contact.
• Name it Default Sendto Slack.
• Click on Sendto Slack tab on the contact screen.

• Click on Use Default URL radio button – To use Incoming Webhooks that is given on Dashboard -> Config -> Integration -> Sendto Slack tab.
• Click Save button. Please make sure you don’t skip any step from 3 to 5.
• Then click Test Link to test your Incoming webhooks. You may close the contact screen once you get the test message in the desired channel of Slack application.
• Still, confusion, click on this link to get help.

You can send alerts directly to your customer’s Slack’ channel by providing the Incoming Webhook URL in “Use Custom URL” field.

Each time, you create any contact for “Sendto Slack” plugin, make sure to test it by clicking on “Test” link before using it in production.
Create Default Alert Template and Add Alert Action.

• Navigate to System-> Configuration ->Dashboard -> Management -> Alert Templates.
• Click on New Template name it Default Sendto Slack.
• Click on Add Alerts button to add New Alert Action.

• It will bring a new window called Edit the Alert for Default – Sendto Slack.
• Click on New Alert. Again, a new window comes up called Alert Item Settings window.
• In the Alert Actions section, scroll down to find Sendto Slack alert action.
• Check the checkbox for ERROR column of Sendto Slack alert action.
• Select Every day.
• Select Contact. That is Default Sendto Slack contact. You’ve recently created it as mentioned in the above section.
• Click Save and Close button.

Now, you can use this Alert Template with any monitor to send alerts on the Slack Channel.

The post ConnectWise Automate Integration with Slack appeared first on SankalpIT - Plugins for Automate.

Requirements

What are the prerequisites for this Script?

Requirements on the target machine.

How does the script work?

1. 1. Create a ticket to record the upgrade process. On upgrade success, the ticket will be closed with proper time entry. Else, it remains in the open state.
   2. Disk Space: the Script checks the all drives internal drives on target machine choose the one that has maximum free disk space to store the windows setup file (and other related files). The target machine must have at least 10GB free disk space on any drive and 5GB on the system drive.
   3. If Laptop: Laptop should be on charging mode if the script finds it on battery mode then exit with ticket comment.
   4. Windows 10 setup file. Script downloads setup to file %Drive%:WindowsSetupFolderWindows10.iso. location.
      – First, the script tries to copy the windows setup file from the Location Cache directory %cachedir%Windows_10_x64_Pro.iso to %Drive%:WindowsSetupFolderWindows10.iso.
      – If it couldn’t find the file in the cache directory, it tries to download the ISO from LTShare folder.
      – If it won’t find ISO file on LTShare then exit with a ticket notes.

Note: Please make sure you set up a network (cache) directory on the location if you want the script to copy the required *.iso file from a network drive. Please take look on how to setup Cache directory documentation given on Docs.Connectwise.com. https://docs.connectwise.com

1. 1. UpgradeKeyChecker utility: It downloads the UpgradeKeyChecker utility to the setup folder.
   2. Check User logged in: If a user logged into the system and working on the system, then script sends message to the user asking for permission to upgrade. If it doesn’t respond or says no to upgrade, then the script delays the upgrade and It runs after run after 9 hours. It asks the same question if the user logged in, but this time it is not rescheduled for next run. It simply exits with ticket notes.

Note: If you want to run the script on such machine where it had been rescheduled, but the upgrade didn’t take place then you need to uncheck the checkbox called “Asked user No. of Times” from Windows Upgrade tab of the Computer Management Screen.

1. System Restore Point: It creates a system restore point on the machine.
2. Export last logged in user reg file: The script exports last logged in users that it imports after the upgrade.
3. Upgrade process: it runs the upgrade process using UpgradeKeyChecker utility that requires a license key to run, and you should be able to browse https://license.sankalpit.com/ on the target machine.
   

   Supported parameters:

   • Setup.exe path: %Drive%:\WindowsSetupFolder\setup\setup.exe.
   • Script License Key: We will send you an email having your Key. That you will need to provide in Function Script to upgrade Windows to Windows 10 script. Open this script -> Globals and Parameters tab. Then, select scriptkey variable and enter your license XXXXxxxxXXXXxxxxXXXX there and click Save button.
   • Windows License Key: You can assign Windows License key in the EDF called Windows License Key on the Computer Management screen to use in the script. Windows setup will upgrade Windows to the specific edition by checking the license key.

   With license key, you can upgrade Home Basic (or any other Home Family OS versions like Starters, Home Basic, Home Premium, etc.) 32bit machine to Pro, Enterprise or Ultimate 64bit Edition. It all depends what License key you’re using to upgrade.

4. Import Last logged in User’s Reg file: After the upgrade, it imports the last logged user’s details to the registry. It helps users who don’t remember their user names.
5. How much time it takes: it depends on the performance of the machine, but it usually takes 40 to 60 minutes.
6. Ticketing: Script records everything (failure or success) in ConnectWise Automate ticket to check.

FREQUENTLY ASKED QUESTIONS

How does the profile migration work? How many profiles are migrated per computer?

– Windows setup handles it very smoothly. Users won’t see any difference then Windows 10 graphics and working environment. This upgrade is the same as you upgrade your windows 7 to windows 10 by the double-clicking Migration tool.

Are any backups performed?

– The script creates the system restore point. However, we recommend you to take a bare mental backup before running the upgrade. As you always have a backup if anything went wrong.

However, I have seen if anything went wrong with your machine upgrade process will be canceled and it restores to windows 7.

Is that easily adjustable to update to the next latest 10 when it comes out, and we are ready to deploy?

– Yes, It depends on what Windows 10 version you have placed on LTShare folder. I Upgrade Windows 7 to Windows 10 1703, Windows 10 1803 and Windows 10 1903. It the matter of setup file you give the script to run.

Is it possible to get it to do mostly in the background?

– It is a major upgrade as we know, we could not make it 100% silent upgrade, but yes, we were able to make the script to do 60% of its job in the background. Windows upgrade requires several reboots that’s why we couldn’t make it 100% silent.

Can supply license keys to upgrade to specific Windows 10 edition?

– Yes, you can migrate Windows 7 32bit machine to windows 10 64bit if you supply Windows license key. Windows upgrade checks the license key and runs the upgrade accordingly.

Can I upgrade Windows 7 unlicensed to Windows 10?

– Yes you can. We recommend supplying windows license key with the upgrade.

Does it support HostedRMM?

– No, It doesn’t support HostedRMM.

Does it upgrade Encrypted Machines?

– Attempts an upgrade without suspending BitLocker. If the upgrade fails, Windows Setup will suspend BitLocker and complete the upgrade.

If fails again, then it is recommended to remove the encryption and run the script again.

How do I troubleshoot the upgrade related issues by myself?

If the script doesn’t work for you, and you don’t know why!

Then, run the Command prompt as Admin and run the following command. The script runs the same command as the System user account.

• Without Windows Key:“C:WindowsSetupFolderupgradeKeyChecker.exe” /setup “C:WindowsSetupFoldersetupsetup.exe” /scriptkey XxxxXXXXxxxxXX
• Or with Windows Key:“C:WindowsSetupFolderupgradeKeyChecker.exe” /setup “C:WindowsSetupFoldersetupsetup.exe” /scriptkey XxxxXXXXxxxxXX /windowskey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Please don’t say, WindowsSetupFolder directory exists in D:, E: or any other drive and what do I need to do 🙂

Why IIS wasn’t downloading the big files – the .iso files? what is the solution?

– The problem was the .iso file not being defined within the MIME Type in IIS.
– To resolve we have defined .iso as the MIME Type in IIS.

Need to follow the mentioned steps to set MIME Type for .iso files:

1. Open IIS Manager (Start >> Run >> type inetmgr hit enter).

2. Select the root node from the connections pane. Double-click MIME Types from features pane.

3. Click on Add link in the Actions pane. This will bring up the dialog box. Enter file extensions, specify corresponding MIME type and click on OK button.

File name extension: .iso

MIME Type: application/octet-stream

4. Restart your IIS Server from IIS Manager.

Term and Conditions: Click here

The post Upgrade Windows 7 to Windows 10 appeared first on SankalpIT - Plugins for Automate.