Thank you for the prompt response.
Yes, I can manually copy the patches to the target machines patch folder.
I am using a Distribution server.
The machines are not wireless or connecting across a WAN
On the Target Machine:
I followed your instrutions. The patches successfully copy to the patches folder now. However they do not automatically install and the prompt that the machine will be rebooting does not come up. I can manually install the patches from here, but that is not quite the end result I'm looking for :-).
I did notice in the "scheduler" folder there is a scheduler.txt document. It appears to be giving a few errors:
**TIMESTAMP** No job queue file: C:WINDOWSProPatchesSchedulerstJobQueue
**TIMESTAMP** AcquireContext failed: 0x80090016. Container Name = **long string of characters**
**TIMESTAMP** AquireCreds failed: 0x08009030d
**TIMESTAMP** ClientConnection.cpp:204 Abnormal connection termination
-- The last entry is repeated three more times --
Any ideas based on what I'm seeing? Thanks again for the support.
On the console, Clear, then set your currently logged in user credentials within Tools -> Options -> Default Credentials.
Create a new machine group, enter the required machine by IP, and don’t enter its credentials.
On the target machine, stop the Shavlik Remote Scheduler Service.
Delete the c:windowspropatches folder
Using regedit delete HKEY_LOCAL_MACHINESOFTWAREWow6432NodeShavlikScheduler
Scan the new machine, and then deploy a single patch to the machine again using the Standard deployment template.
The scheduler service files should get recreated and the service started automatically
That fixed it! Thanks for the prompt replies and above all thanks for the solution to the issue.