Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot I then install all windows updates including FU with: With 200 computers, it could be a worthwhile investment of your time.Install-Module -force -Name PSWindowsUpdate If you don't know PowerShell or use remoting, I recommend you learn a bit about both. You could use PowerShell like this $Computers = '', '', '' Invoke-Command -ComputerName $Computers -Script If you get remoting working, then you can use KACE to push your uninstall/install batch file to the clients, then use PowerShell to run the batch file. If your computers are in Active Directory, it's not hard to setup a Group Policy to enable remoting. I frequently use PowerShell remoting to connect to computers using the command line. I don't think trying to use KACE to uninstall the beta agent and install the stable one will work. I believe the problem is that the batch file runs under the context of the KACE agent, so when the KACE agent is uninstalled it kills any processes it started. Anyone have any similar things that they have done that have worked? Batch file gets to where KACE is uninstalled and then stops. Call the batch file (not in KACE) from a script. Put batch files and other files synced to a location outside of the KACE installation. I would rather not have to roll back by manually uninstalling/reinstalling the agent on around 200 machines.Īgain, this is what I did. I am wondering if anyone else has experience with this and what they have done. I'm not exactly sure if that is what is happening. I'm guessing it is because KACE somehow is hosting the batch file. I then used a script to call on the batch file (which I should think would run all the way through.) However, when I get to the part where KACE is uninstalled, I believe it stops. I created a batch file stored outside of the KACE install location. I know that sounds really weird, but hear me out. I am trying to uninstall KACE and reinstall, through KACE. However, when that happened, the file sync is now intermittent and deleting random files every time that the devices check in. I made the silly mistake of having them auto update to 11.0 (Beta, I know). We were using the 10.0 agent with no issue. We currently have around 200 machines that use File Synchronization. I know how this may sound weird, but here goes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |