Search the Community
Showing results for tags 'server'.
Found 2 results
We upgraded our SmartDeploy install to 2.0.3050 and everything was good. Then we started our Windows 7-10 upgrade project. - When trying to use the USMT capture on some of our older clients SmartDeploy helpfully told us we needed to upgrade to a different client version for the USMT functionality (2.0.3035 I think?) and that's where the problems began. The server we used for our initial installs using smartdeploy no longer exists, but when trying to install the latest client using an MSI, it fails as it can't find the installer from the original location. - So it doesn't update. So we tried pushing the Installer via a GPO. - it updated our Win10 machines, but not the win7... - update fails. Then, in an almost last ditch effort first - All machines with an agent version earlier than 2.0.3050 were removed from the SDE Computer Management console. Then - All of the offending workstations, the SDE server, and domain controllers were rebooted. but even after days, the win7 machines haven't shown up in the console. Is there a script / Command I can run to purge all traces of the old agents, so the new agent can install, which will allow us to USMT all the things, and get this project back on track? The error it throws is 1714 the previous version of smart deploy could not be removed. contact your technical team. Help me DeployCentral! you're my only hope...
While imaging less than 10 computers at a time (sometimes less than 5 computers), we are getting reports from our network infrastructure team that network bandwidth is maxed out and saturated to the point that all users on campus cannot utilize any network assets. We have a 1GB backbone/switches throughout campus and all imaging communication resides on premise inside our DMZ. We usually image via unicast to our WDS server and expect to be able to image up to ~25 without speed issues before going with multicast transmissions, but are still having network speed issues with less than 10 at one time. We have been able to image successfully in the past without speed issues, but we are trying to pinpoint what has changed since then causing our bottle-neck. Our image size has actually decreased in size to 10.4GB. Any input is appreciated.