Aaron@Shared

I am noticing an odd error when imaging thru the Console. It has just happened recently and not sure what the change is. Here is the error: I am not sure the cause and it is not preventing any imaging. But want to know why. Specs: SmartDeploy version 2.0.3080 Windows 2012 R2 (slow) Thanks, Aaron

Add the following into your answer files:

Every single time you change anything: 1. SD Upgrade 2. Answer file change. 3. Image change Hope that helps. Edit: Welcome to SmartDeploy! I got this working for my IT Department and been using for about 2 years.

@tomsiemers I would recommend getting a tool good NTLite. It allows you to perform a lot of debloating on the ISO as well as create an unattended install. The free version only limits you on removing specific items. With this tool you can download the latest updates as well as integrate .Net 3.5 if needed.

@tomsiemers I use Chocolatey in my golden images to install most of the major software we use. Browsers, PDF, Office365, Teams, etc.

Try this: This is in the Advanced options of the Answer file. Make sure you have this line. If not, it might be causing your issue.

I have used SD with 7060s and 7070s without any issue, but I am using either PXE boot or Network deploy from the server.

No because I have -10000% control over the servers. But its very slow scrolling, searching for a PC. Oh and don't get me started, downloading a driver pack will sometimes freeze at 51%. If it were up to me, it would be running on a non-VMed 2019 server outside of the internal network. So thus...I doubt that SmartDeploy plays any part in this. Its my server/virus protection thats causing my issues. However my IT manager wants us to get a tool that does EVERYTHING all in one. Imaging, auditing of hardware and software, software install, etc.

I am in need of some assistance. I want to make bootable USB drives from my SD server but I cannot. My server is a virtual server and thus no physical USB ports. If I go thru the Deployment pack creation, I realize I can create a DVD but this then does not give me a bootable USB. It creates 2 ISO files and this does not work. I wish our SD server was its own server and running Windows Server 2019, but oh well. Does anyone have any thoughts on how to do get this done? Thanks, Aaron

Randy, what exactly is happening when you image an PC? Is it not booting up? Did you try the above method? Aaron

Good afternoon. We are running SmartDeploy on a 2012 R2 server and when navigating in the SD Window, it is laggy. Esp in the Computers window. The server has 16GB ram and running on a 1Gb ethernet. It is NOT a server by itself but virtualized. Is this the cause of the slowness? Could someone please offer any tweaks or recommendations to help the performance? Also we are using Sophos for our AV solution. Thank you, Aaron

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.

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.

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.

In the run command or Windows 10 search after click on Start.

tonys, I would recommend submitting a support ticket with any log files attached.

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.

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.

Chris, that is a no. I haven't seen this feature and we have been using SD for over a year.

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.

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.

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.

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

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.

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.