Our dedicated Product Specialist team is always ready to help you when you need it the most.
Contact Support
Specops Deploy OS
Resolving UEFI/BIOS error caused by new ADK (v. 2004) issue
Due to code changes in Windows ADK 10 v2004, the MDT utility (Microsoft.BDD.Utility.dll) that identifies BIOS or UEFI firmware types no longer works correctly, and identifies BIOS-based machines as UEFI-based machines. Symptom Deployments will fail with the following error: FAILURE (5616): 15299: Verify BCDBootExLitetouch deployment failed, Return Code = -2147467259 0x80004005Failed to save environment to...
How the Specops Deploy licenses are being counted and how to free up seats.
The license count The requirements that needs to be fulfilled for taking up a license seat are that the Specops Client Side Extension is installed on the machine and that a Specops Deploy configured group policy Is applied to its computer object in Active Directory. After a group policy update on the machine a computer...
Windows Pre-installation environment (WinPE) fails
Possible cause Certain OS components, like device drivers, that are a required for WinPE to work, may not be present. WinPE cannot connect to the Deployment Share of your Deployment Server. Possible solution The required drivers are pre-loaded in the boot image and may need to be added to the driver repository. The version of...
Connection timeout
Possible cause The configured timeout value is too short. Possible solution Increase the operation timeout value, using the registry settings:
No connection could be made because the target machine actively refused it
Could not connect to net.tcp://computer.domain.local:4375/ Specopssoft.OSDeploy/DeploymentServer. The connection attempt lasted for a time span of 00:00:01.0010531. TCP error code 10061: No connection could be made because the target machine actively refused it Possible cause When adding a remote deployment server, the tcp communications is required to establish communications to the specified port. The timeout will...
How to do In-place upgrades with Specops Deploy OS
Here follows instructions on how to perform an in-place upgrade with Specops Deploy OS. This is for Windows 10 1909 in-place upgrades but the same steps goes for any Operative System. Keep in mind that all Specops components must be of version 7.0.19283.1 or later for 1909, if this will be used for 20H2 in-place...
Getting Specops Deploy working with UEFI
For getting Specops Deploy working with UEFI, here’s what you need to know: Use IP helper addresses on your switches/routers instead of DHCP Options 66/67 – Option 66/67 requires that you set a boot file name and it can only be a BIOS or a UEFI file. Simply setting an IP helper address for the...
Deploy / OS Training Series (part 3): Configuration
Welcome to part 3 of the Specops Deploy / OS training series. In part 1, we provided an overview of the environmental preparations. In part 2, we provided some supplemental information that can be used alongside the installation guide. In this final part, we will walk you through the configuration tasks. Let’s get started! Create a...
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...
Enable .Net in your client OS
.NET is a programming framework created by Microsoft that developers can use to easily create applications. .Net applications are commonly used by desktop and web services. The .Net framework must be installed on your client machine in order to run .Net applications. .Net 3.51 is not installed natively as a part of the OS. Administrators...