https://support.na.sage.com/selfservice/viewContent.do?externalId=92996&sliceId=1

Thanks very much for the article Kevin. I went through everything related to permissions, temp folders, etc., but the process would still just disappear from the screen, and that was after a significant amount of time. I compared the local client files and folders that were created, specifically the C:\ProgramData folder on the local machine and compared that to the same folder on the terminal server. I noticed that all of the autoupdater files were missing. I copied the terminal server autoupdater files to the local machine and hey presto, the client launch worked. 

Thanks again

John

I had this happen once. We finally found that one workstation had UAC turned off. We enabled it, and they received one of those "do you want to allow" prompts. They said yes, and then the workstation sync was completed.

That's very interesting Wayne. Typically I will disable UAC using the regedit command, then reboot, prior to installing Sage. After the installation is complete and I've been able to login, then I will re-enable UAC and reboot again.

We do the same thing, but when UAC is disabled you still need to do everything using an local admin account.  What Wayne describes is what would happen if the first Sage login was attempted using a non-admin account.

We ran as administrator several times, and every time we would kick off the workstation setup, it would just not finish. No messages or errors. I wasn't there when they resolved this but was told enabling UAC briefly, so they received the "do you want to" type prompt was what did the trick. 

The same type of scenario - out of 1/2 dozen workstations, only one failed to let us install the workstation setup.

The other trick is to rename that C:\Sage folder to c:\old.sage\ and then try the workstation setup

Thanks Wayne.

I just had this happen two weeks ago. We found out that Workstation Synchronization needs to run VBS scripts to complete the process. IT had turned off all VBS access on workstations because they had a Ransomware attach a few months back. As soon as IT enabled VBS on the PC's everything ran and completed normally. There is an article about this on the KB. Just search for Workstation Synchronization does not complete .