Here again your favorite Random Dude,
Hope everything has been going well for everyone. today I have an interesting post (at least for me) that used to be a great KB article but that was taken down. I started with KACE when it was at 6.0, a really long time ago, back in those days they were part of Dell. They used port 52230 to communicate with the main server, which started to change by 7.0 to 443 until today when it is only 443.
A good bunch of my friends got stuck on older versions (a company not wanting to upgrade, having some really custom SQL Ticket rules, or any other reason), and jumping to 8.0 (or anything newer) would take ages because you would have to wait for an agent to do an inventory to get the newer one and doing this every version was a nightmare.
Back in those days, KACE published an amazing KB that would provide an example bat file to use to avoid all of that so you could just jump to the latest release and leave your GPOs to take care of the update (or reinstall) of the agent. Thankfully I printed out that KB to PDF so here you have it!
All credits to the KACE person who made it back in those days!!!
- Download the files from here.
- In a file manager browse to \\SMA_Host_Name\client\agent_provisioning\windows_platform and copy the Agent to the local machine
- Move the KACE Agent install file to a "Public share folder"
Download the Batched Script example and change the following:
- "Public share folder" (line 107)
- "KACE Agent installation File name" (line 114, 116) ALSO, if you're going to version12 remember your token!!!
Configure a Computer Startup Script:
- Log on to a Windows Server domain controller (DC) with a domain administrator account and follow the instructions below.
Create a new Group Policy Object in Active Directory:
1. Open Server Manager using the icon on the desktop taskbar or from the Start screen.
2. In the Tools menu, select Group Policy Management.
3. In the Group Policy Management Console (GPMC), expand your Active Directory (AD) forest, domain and click the Group Policy Objects container.
4. Right-click the Group Policy Objects container and select New from the menu.
5. In the New GPO dialog box, give the new Group Policy Object (GPO) a name and press OK.
6. Now right-click the new GPO in the right pane and select Edit from the menu.
Add the startup script settings to the GPO:
1. In the left pane of the Group Policy Management Editor window, expand Computer Configuration, Policies, and click Scripts.
2. In the right pane, double-click Startup.
3. On the Scripts tab of the Startup Properties dialog, click Show Files. Copy the file(s) you want to run to this location.
4. Once the script you want to run has been added to the GPO, click Add on the Scripts tab.
5. Click Browse in the Add a Script dialog and select the file using the file browser. Additionally in the Add a Script dialog, you can optionally specify parameters to configure how the script runs. Click OK to continue.
You can add additional scripts and set the order in which they run by using the Up and Down buttons. Also, PowerShell scripts can be added to a separate tab and set to run before or after scripts specified on the first tab.
6. Complete the configuration by clicking OK in the Startup Properties window.
7. Close the Group Policy Management Editor window.
Finally, link the GPO to an OU, domain, forest, or site:
1. Back in GPMC, decide where you want to link the new GPO. Right-click the desired OU, domain, site, or forest in the left pane and select Link an Existing GPO from the menu.
2. In the Select GPO dialog, select the GPO you just created and click OK.
3. The startup script will now run on computers that have the GPO applied
I tried to keep the instructions as raw as possible, so any comments or additional tips are always welcome in the comment section.