Ups worldship windows server 2008 r2

Then open an elevated Command prompt and again type NET USE revealing the same mapped drives as still present but broken in an error state, unable to connect. This issue is commonly misreported and misunderstood as a symptom of user specific drive mappings, where a user who maps to network drives and subsequently logs off and back on as another user perhaps Administrator will not see those maps drives, as they are stored in the user registry and are therefore user specific.

It seems that Run As Administrator is a somewhat misunderstood function in Windows 7. Some apparently believe this to be identical to using Run As in Windows XP and providing alternate credentials, typically a local or domain Administrator, after which the spawned process would be running under the alternate user context, complete with that alternate user's registry including mapped drives and such. However, Run As Administrator in Windows 7 retains the current user context and registry but demands elevation for the spawned process instead.

The evidence of this difference in the Command prompt example above is simply that the NET USE under an elevated Command prompt shows the same mapped drives as seen in the unelevated Command prompt.

The user context, and thus the registry, is not changed, but for some reason the elevated security token can not access the mapped drives whereas the unelevated security token provided by default can. If Run As Administrator on Windows 7 behaved as some people mistakenly believe it does, i. Once the EnableLinkConnections fix is implemented, the elevated Command prompt will be able to access the mapped drives and UPS Worldship, and other programs that use mapped network shares, will function normally even while elevated.

I am somewhat disappointed, but not surprised, that UPS Worldship does not implement this fix as part of its installation. The expectation from UPS is that Worldship will be executed from the Administrator account itself, not just from a user account that is a member of the local Administrators group.

However, the need for a mapped network share will typically force the use of a domain account as the primary user context for running Worldship, and best practices on the part of many Administrators will cause them to install the software while logged on as local Administrator or a member of their Domain Admins group, and then switch to their domain user for launching the software. Asked 10 years ago. Active 10 years ago. Viewed 3k times. Improve this question. Bart De Vos What brand UPS most manufacturers provide an application that is better than the Windows one anyway, but I see your preference to the simplicity.

Add a comment. Active Oldest Votes. Improve this answer. Jim B Jim B JamesRyan JamesRyan 8, 2 2 gold badges 23 23 silver badges 36 36 bronze badges. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! Same error after that. Also, can you not use Cobian Backup to backup the database on a daily basis to a network drive, in case of issues? This is something we fought with a company over for about 6 months, and when UPS finally flat out told them they wouldn't support it at all, which is what we told them they would say, they got a standalone machine to do what was needed.

As far as the people leaving their machines on, tel them to leave the machine on, develop a backup solution, and have a shutdown scheduled for the machine in Task Scheduler or the backup solution shut it down when it's finished. Sooooo, why not install a master an client setup with the worldship data stored on an directory at the server? If you're doing a fresh install of , it won't work. You'll need to install or first. I never installed it via a server with TS enabled, and wouldn't be surprised if it doesn't work, as TS enables a lot of voodoo when it comes to program installations, and are exceptionally unfriendly with programs that require interactive sessions for install.

Moreover, you shouldn't require TS enabled for UPS WorldShip, as it's built to deploy remote workstations via installer, not running multiple instances on the same workstation. Additionally, if you think about how UPS WorldShip deploys its security restrictions, the permissions are assigned per workstation, and not per user account.

In a sense, it's really built for client deployment above all else. In the end I finally convinced them to let me install on one of the accounting systems they will be taking over the role anyways and informed them that if they are to be on vacation or what every they need to leave their system on.

Was trying to deploy WS to 32 bit TS. In the end it is on W7 and using Robocopy to ensure archives are moved to server folder. I am still looking hoping some of the long shots they are working on work out so I don't have to leave. Hm, maybe it's because I'm still running Perhaps I'll finally upgrade this weekend if I have time and see what's different about it.

If I find anything I'll let you know. Again, TS role may be what killed your install, so if you can run a VM with just server alone and replicate my environment, you might have a better chance of completing the install.

You will NOT be able to recover anything other than a week out from your last archive. The system backup is your prefered backup.