Jump to content
DeployCentral

Aaron@Shared

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aaron@Shared

  • Rank
    Advanced Member
  • Birthday 07/20/1978

Profile Information

  • Gender
    Male
  • Location
    Northwood, OH

Recent Profile Visitors

291 profile views
  1. It has been my experience with previous SD Client releases, that the clients themselves auto update from the server. Edit: You will also have to update ALL of your deployment packages (including WDS) for it to use the latest client version.
  2. Could you provide a fix for the rest of us? I ran the above fix and in the command window I am getting this message repeatedly: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 0 - [x89C50118]) This is on a Windows 10 machine and not on my server. Not going to risk breaking SD on our server with this version until this is resolved.
  3. You have to create a new WDS Deployment for WDS to work. It cannot use the Deployment media created within SD. Run the deployment wizard and select WDS, then proceed. It will put into a \Media folder under SmartDeploy.
  4. In the run command or Windows 10 search after click on Start.
  5. tonys, I would recommend submitting a support ticket with any log files attached.
  6. mnewman, Make sure that when you are done with your Golden Image, that you close the image with shutdown.exe /s /t 0. This will ensure the VM is shutdown properly. Then capture it.
  7. Michael, are you telling where to map the drive in your Answer file? If this is not in your answer file, then its not going to PXE correctly. Also, make sure you update your WDS Image with the new answer file from within SD and in the WDS Server itself.
  8. Chris, that is a no. I haven't seen this feature and we have been using SD for over a year.
  9. Also, make sure your computer's BIOS is configured for network boot. Our Dells are coming to us with PXE boot turned off. You will also see option for Secure Boot. We are leaving this on and have no issues with SD PXE imaging.
  10. Sam, from my experience, if you take a computer and install an older version of the client on it, it will show up in the SDE Computer Management console and then it will update on its own without you having to do anything. Hope this helps.
  11. I build all my images on a PC with the server client installed, then capture the image there and then transfer it to the server. I find my 2012 server to be very slow as well, but then again its not a physicaly but a VMed server. Hope this helps.
  12. Try this command in your answer file under Advanced, then Tasks: Set this task to be after image is applied with the following command: bcdboot C:\Windows /p /d
  13. SURE RECOVERY HAS TO BE DISABLED FOR IMAGING TO WORK. If not, it will prompt on every single BOOT if you want to restore the computer. This is done via BIOS.
  14. Dale, every time you make a single tiny change to the answer file, you have to rebuild ALL deployment media. I would give this a try.
  15. I have installed 365 with teams onto 4 of my images. All 4 work flawless when I image a PC and then authenticate into Office365 with their credentials. I am not downloading and installing from a EXE. I am using the 365 deployment toolkit and performing the install thru CMD and silently. Also, I am NOT opening any of the office apps before closing the VM.
×
×
  • Create New...