Knowledge Base

Our dedicated Product Specialist team is always ready to help you when you need it the most. Contact Support

Specops Deploy OS

PXE boot error: ‘No DHCP or proxyDHCP offers received.’

The client machine doesn’t retrieve an IP adress. This is happening very early on in the deployment process, before Specops Deploy is seriously involved and the connection with the Deployment server/WDS is established. This is most likely a network related issue and we recommend to start with the simplest thing: to check your physical network...

Migrate Specops Deploy OS to a new server

Here follow instructions for a Specops Deploy OS migration to a new server. This is a complex process and our advice Is to be careful and not rush through the steps. We also offer consultancy if you want a Specops product specialist to carry out the migration for you. Pre-requirements Make sure to remember this...

Drivers missing

Possible cause The required drivers have not been added to the driver repository. The WMI name for the Make and Model of the computer may not have matched correctly during installation. Possible solution Add the drivers to the driver repository. Visit your computer’s manufacturer’s website to download the drivers you want to import. If you...

Error when publishing: Specopssoft.OSDeploy/ImageServer Did Not Receive a reply within the configured timeout (00:30:00)

When publishing a new driver in Specops Deploy OS you may receive the following error message: Specopssoft.OSDeploy/ImageServer did not receive a reply within the configured timeout (00:30:00). This happens when the publish takes longer than the expected 30 minutes. The fix is quite easy. Browse to the following settings in the registry, and change the...

PXE booting fails

Possible cause Network switches may not be configured properly. This does not allow the clients to discover all available Deployment Servers by broadcasting. Possible solution Your network switches must be properly configured to work with PXE.

Install new deployment server, error: The required registry value ReleaseId on the key LocalMachine:SOFTWARE\Microsoft\Windows NT\CurrentVersion is missing

We have occasionally seen this error when the Image server operative system version or build Is older than the Deployment server operative system. A registry mismatch of some sort has most likely occurred. Installing the deployment server MSI manually on the new deployment server usually solves it. On your Image server: 1. Close the Specops...

“Access is Denied” error when importing an OS from DVD

Possible cause McAffee Antivirus Possible solution Either disable McAffee Antivirus Realtime Protection while you do the import, or setup exclusions of the DVD Drive and Specops Deploy repository folder.

How to deploy BitLocker with Specops Deploy

If you need to protect your organizational data through drive encryption, chances are, you’ll need BitLocker deployment. This was the case for a Specops Deploy customer that wanted to enable BitLocker on new Windows 10 machines. In this blog post we will walkthrough how to activate BitLocker with Specops Deploy / OS. The process is...

Default reinstall fails

Possible cause The Client Side Extension is not installed on the client. Possible solution Verify that you have a GPO with the Specops Client Side Extension If you do not have the Client Side Extension, you will need to do the following: Right-click on the OU, and click Create a GPO in this domain and Link...

Post OS installation tasks

There are some Group Policy settings that will prevent a successful OS Deployment because the Task Sequences can’t then logon. For example, a gpo with settings like this; Changing the local admin password Interactive logon: Message text for users attempting to log on Rename of the local admin account Enabling Smart Card requirements Enabling BitLocker...
« Previous PageNext Page »