Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About tghowe

  • Rank

Recent Profile Visitors

1,801 profile views
  1. Thanks for that great explanation. My hope was to have the machine autologon using a domain account, then automatically reboot so the GPO settings/software can install and be ready for the end-user without any more interaction from me. Currently after imaging, I log on and hit restart the old fashioned way. Deploying to a single computer is no issue, but an entire lab of 30+ computers takes a little longer. Thanx for your help!
  2. After setting the count to "1", it will autologon into the specified user account. When I reboot the machine again, it automatically logs on once more for a total of two autologons. It doesn't do it a third time. I also cannot set it to zero, nor can I simply remove the inserted credentials without causing a pop-up "you must provide all autologon settings." I was hoping to combine this feature with a TASK which would reboot the machine upon first logon, using "shutdown /r".
  3. Upgraded to the new SmartDeploy 2.0.3005. Anyone know what the "count" setting is for under the new Autologon after deployment option? I didn't see any reference to it in the User Guide.
  4. Sorry about the delay. As soon as I began the "move" process the Dashboard began updating with the list of PPK files. Thanks for the info.
  5. My directory is on D-drive instead of "C", and the dashboard reflects this. I did try setting it to "C" and back to "D", but it made no difference. It's been happening since version 2 was initially rolled out long ago. I think there was only one update where it didn't happen this way.
  6. Running Smartdeploy version 2.0.3000 on Server 2012 R2. Why do I have to manually import each PPK file after running an upgrade? The Images and Answer Files show in the dashboard with no issues, but it seems I have to manually import each PPK file after doing every software update. Since there is no batch import this process takes a while. Am I the only lucky one this happens to? Thanx!
  7. You can also try deploying to your new machines without current platform packs. Windows 10 does a pretty good job of discovering and working with new hardware on its own.
  8. I didn't realize they put out a new version last week, I'm upgrading now (with their blessing). I went thru a number of special builds with them and many changes were made. My case isn't considered officially solved yet until I reach a certain number of clients....currently at 399. We'll see how it goes.
  9. I've been beta-testing a special version which so far shows no problems. I do not know about specific version fixes.
  10. Hi jlinane, I have been working with their developers the past few days but as of yet no solid solution....but I think we are close.
  11. SUPPORT TICKET PLACED I recently upgraded SmartDeploy to version 2.0.2010, and successfully deployed the client app to most of our workstations. Yesterday was fine, but today however I cannot keep the SmartDeploy Console running! The error below occurs several minutes after trying to select a library (pics attached). If I do select any of the libraries, it takes a long time for the list to populate.... if at all. I've tried stopping and restarting the service, as well as rebooting the server itself. Besides the SmartDeploy update, I've also ran Windows updates this week....but nothing today. Server specs are: Windows Server 2012 R2 Datacenter..... 16GB ram.... 432GB free space on OS drive....
  12. Any help with this? I'd really like to test this out.
  13. Thanks! Unfortunately I get the dreaded "The page you are trying to access is not available for your account. Error code: 2C171/1" when I click on the link. So the " autoadmin.vbs" file is to be located on the client, right?
  14. We just upgraded to version 2.0.2010 and we've been experimenting with unattended deployments. We have several domain GPOs that load when SmartDeploy places the client on our domain, but they don't take affect until the client gets restarted. At this point we would normally log into a client and restart it manually. What we'd like to do is have the client restart after all other deployment steps are completed and we're staring at the domain login prompt. This would allow true unattended deployment without user interaction.....such as a lab environment and/or after hours. I've tried modifying the answer file by adding "tasks" under the "advanced options", but it did not trigger at the right time. Any ideas on how we can make this work? Thanx in advance!
  • Create New...