Jump to content
DeployCentral

SteveE

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SteveE's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. The resolution was to use the Tools Tab in the SmartDeploy console and click "Generate Client Installer". This is a new requirement in Version 3. WOuld have been helpful information to have. Using this generated installation file, it installed successfully.
  2. Well that didn't work....I guess I will contact support.
  3. Thank you, Jeff...you make great points there! I learned in the past that JumpStart will interfere, so I always disabled that service first. These latest HP machines don't have JumpStart anymore. I did disable all of the running HP services, but I will try uninstalling the software and trying again.
  4. I just installed v. 3.0.1005 SmartDeploy - that went fine. Opened brand new just out of the box HP PC. (EliteDesk 800 G6 - Mini PC). Running Windows 10 20H2. Attempted to install client, but every attempt to do so I get this error during installation when attempting to start the SDClientService: "Error 1920. Service SmartDeploy Client Service (SDClientService) failed to start. Verify that you have sufficient privileges to start system services." Only option is to Retry or Cancel. Retry gives the same error message and Cancel rolls back the entire installation. I am running the install as an administrator on the machine. (Tried both domain admin and local admin accounts.) Troubleshooting Steps: 1. Tried to install after both after joining the domain and disjoining domain. 2. Ran msconfig to do clean boot - only Microsoft Services were allowed to run and killed all Start Up processes in Task Manager. 3. Tried both x64 and x32 versions of the client install. 4. Copied Installation files directly to local hard drive for install. 4. Tried installing on my main computer and it failed the same way (computer is about 4 years old with a lot of stuff on it, but just wanted to see if it would work). Not sure what else to do. I ran the install with logging so I have the log file if a SmartDeploy tech wants to look at it. Error attached.
  5. Yes I was referring to the Antivirus licensing, not Smart Deploy licensing. Your response is what I figured. Thank you.
  6. Out of curiosity, is there a way to execute a command or script BEFORE the computer shuts down and boots into Windows PE? What I would like to do is run a silent uninstall of the Antivirus software before shutting down and going into Windows PE for imaging. This would eliminate me having to go log into the AV management console and remove the computer manually. What happens is after I apply a new image to a computer I run a script on first boot to install the antivirus. The management console doesn't care that it's the same computer name and IP, it just creates a new entry with a unique identifier during installation. So now in the management console I have duplicate entries of the same computer name and it uses up two licenses now until I delete the old entry.
  7. Is there no work-around that you guys have discovered, aside from a user having to rebuild a profile or rebuild the image?
  8. Hours of work went into building my reference VM. I can't just wipe out and recreate user profiles every time I re-image a computer, that defeats the purpose of migrating the user data. There ought to be a way to fix the profile itself without recreating it. On a side note, I verified using a test account that wiping the profile and starting new does, in fact, fix it for that user.
  9. I am at my wits' end right now! I have been messing around with this and trying so many different things to get this to work, but no dice. After deploying an image to a computer, users are unable to open the calculator app. This is kind of a big deal for them. I've been Googling all day and tried it all. I've mostly been concentrating on figuring out how to get it to work post-deployment. For local and domain administrator accounts I can run a Powershell script to make it work - for that user only. It doesn't fix it for all the users of the computer. If anyone has run into this and has a way to resolve the problem, please let me know! I could really use some help here.
×
×
  • Create New...