Hello, I have been researching a deployment plan of systems with Windows 10 pro with the out-of-box experience for customers. I am having difficulty setting this up. Read many documents particularly from Microsoft but they appear to be vague. Is there a simple step by step instructions to create an OOBE configuration for Windows 10?
Thank you
Hi,
On our 2019 server we are no longer able to PXE boot from WDS with MDT lite touch image after installing the March 19 cumulative update, kb4489899.
We are getting the following error: A required device isn't connected or cannot be accessed.
Other people are reporting this issue on server 2012: https://www.reddit.com/r/sysadmin/comments/b08coa/patch_tuesday_megathread_20190312/eifnzlq/
Hi
I wonder if someone can help. I'm installing UEFI windows using WDS and an answer file.
Once the client connects to the WDS share, downloads the image etc. and reboots I'm getting the "no bootable device" error. I discovered (quite by accident) that if I then reboot and enter the boot menu, selecting Windows boot manager under UEFI will then continue with setup and eventually lead to OOBE.
If I deploy the same image without an answer file and let it set up it's own partitions etc I don't get this behavior on the reboot. My answer file has will wipe disk in the PE section , followed by creating and then modifying 4 partitions etc. As manually invoking the UEFI boot manager works, it's clearly doing this part fine.
I am presuming that somewhere I need to tell the machine to invoke boot manager on restart but I can't see where or how. Anyone able to help?
We have a HP DL380 Gen10 server that has the BIOS set to UTC time. This server PXE boots and loads a custom WinPE image. When WinPe boots up, we are setting the timezone to Central via a reg import and running a net time /set command to sync with the deployment server. The time gets set to what it should be.
But, we noticed recently that at around 45-75 minutes, the time will jump ahead 5 hours.
If I change the client server BIOS to local time, then the issue does not occur. Flip it back and the issue comes back.
We use WinPE as the environment to configure bare metal servers. Things like BIOS settings, firmware, RAID settings, burn-in testing, etc. The customer may want UTC enabled in the BIOS of the client server but we do not want WinPE to be affected by this. I am trying to figure out what is causing this and how to stop it.
So I have 2 WDS servers one on Server 2012 and one on Server 2016. I setup a Dell OptiPlex 3060 with our WinX Enterprise just like we always do. We have several other models with images on the server that work fine, even an OptiPlex 3060 Micro. When I add this Install image the WDS service fails to restart. I delete the image and it starts right back up again. So it thought bad image, made another one, same thing. So I grabbed another system set it up and made another image and same thing.
Same exact systems on both servers, Server 2016 is a vm and 2012 is physical.
Any Ideas?
Dear Ladies and Gentlemen,
we have been using setupcomplete.cmd in the "sources\$OEM$\$$\setup\scripts" folder of the Installation DVD to add unattended content to a Vista/W2K8 installation after setup completed. We now would like to move to WDS as quickly as possible without rewriting all our scripts. Is it somehow possible to use setupcomplete.cmd with a Vista/W2K8 installation from WDS ? If yes, into which folder do I have to copy the cmd on the WDS server so it gets used by Vista setup ?
Thanks a lot for your help !
Alex
Good afternoon,
In our company we had an issue with our server Windows Server 2016. The first time we set up that server, we saved an admin password and tried to type that password however it doesn't work. For that reason, we decided to boot an USB which contains a WS16 ISO and we executed that ISO through Rufus. We put the USB into the server HPE ProLiant DL360 Gen 10 and then we pressed F11 button to boot that USB. After that, we clicked Next and then "Repair your computer". Then, Troubleshoot > Command Prompt. A cmd was open, so we typed diskpart and then list vol. The problem is we can't see the disk from that server, in the picture I attach, it shows only three volumes: Volume 0, 1 and 2 and the disk is not contained in none of those volumes.
I saw this video to reset the admin password, but I've struggled in the part of the Command Prompt: https://www.youtube.com/watch?v=0afiaKoVoF8
How I can solve this stuff?
Orlando Ávila
My team is currently deploying some new clients using WDS. When we PXE boot the clients to connect to the server over IPV4, it shows an error like the following:
Windows Deployment Server (IP Address)
Windows Deployment Service encountered the following error: Error code 0xc0000272,
Has anyone seen this specific error? I have seen several articles about WDS errors but this one is not mentioned. Thanks all.
JCtech1123, Cheers
I Have an active Directory setup within my office, and I wish to take advantage of Windows Deployment Services to deploy office workstations for our employees.
I have 1 requirement.
The DHCP server is an Mikrotik RouterBoard.
I need to know what options I need to set to allow our clients to PXE boot into WDS.
No one really seems to know what needs to be done.
Since there are options for using a 3rd party DHCP server software, I cant see why this will not work.
Hi,
I install ADK 1803 (version: 10.1.17134.1), and try to customized our own wim file. No matter I use dism.exe built in Windows server 2008 R2 standard or the one bundled into ADK. I alwayes got a error message:
Error: 577
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown sources.
I open C:\Windows\Logs\DISM\dism.log, error log is as follow:
2019-09-11 15:15:50, Info DISM PID=2232 Scratch directory set to 'C:\Users\FUEDA-~1\AppData\Local\Temp\2\'. - CDISMManager::put_ScratchDir 2019-09-11 15:15:50, Info DISM PID=2232 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Getting Provider DISMLogger - CDISMProviderStore::GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Getting Provider DISMLogger - CDISMProviderStore::GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Manager: PID=2232 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Getting Provider DISMLogger - CDISMProviderStore::GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM.EXE: 2019-09-11 15:15:50, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2019-09-11 15:15:50, Info DISM DISM.EXE: 2019-09-11 15:15:50, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7600, Running architecture=amd64, Number of processors=8 2019-09-11 15:15:50, Info DISM DISM.EXE: Executing command line: dism /Mount-Wim /WimFile:"c:\winpe\media\sources\boot.wim" /index:1 /MountDir:"c:\winpe\mount" 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-09-11 15:15:50, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2019-09-11 15:15:50, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2019-09-11 15:15:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2019-09-11 15:15:50, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2019-09-11 15:15:50, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2019-09-11 15:15:50, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager 2019-09-11 15:15:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager. 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Getting Provider WimManager - CDISMProviderStore::GetProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2019-09-11 15:15:50, Error DISM DISM WIM Provider: PID=2232 Failed to mount the image. - CWimImageInfo::Mount(hr:0x80070241) 2019-09-11 15:15:50, Error DISM DISM WIM Provider: PID=2232 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x80070241) 2019-09-11 15:15:50, Error DISM DISM WIM Provider: PID=2232 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x80070241) 2019-09-11 15:15:50, Error DISM DISM WIM Provider: PID=2232 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070241) 2019-09-11 15:15:50, Error DISM DISM WIM Provider: PID=2232 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x80070241) 2019-09-11 15:15:50, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2019-09-11 15:15:50, Info DISM DISM.EXE: 2019-09-11 15:15:50, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2019-09-11 15:15:50, Info DISM DISM.EXE: 2019-09-11 15:15:50, Info DISM DISM Image Session: PID=2232 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider 2019-09-11 15:15:50, Info DISM DISM Provider Store: PID=2232 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
From "What's new in WinPE", Windows server 2008 R2 is supported by "Windows PE for Windows 10". So what shoud I do to fix this issue.
Thanks
Hello,
Below error observed while installing windows feature
PS C:\> Install-WindowsFeature Web-Asp-Net45,Web-Mgmt-Service,Web-Net-Ext45
Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
One or several parent features are disabled so current feature can not be enabled. Error: 0xc004000d
At line:1 char:1
+ Install-WindowsFeature Web-Asp-Net45,Web-Mgmt-Service,Web-Net-Ext45
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
Exception
+ FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWind
owsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No Failed {}
OS is windows standard 2016 with latest patches
Regards, Ajit
Preciso de ajuda para minha usuária que perdeu a senha e a chave de recuperação do BitLocker também não lembra qual foi o e-mail que ela registrou e não conseguiu recuperar os dados do HD dela
Desejo saber como recuperar uma senha do BitLocker, sem essas informações?
I seem to be failing on my searches.
Is there a way to upgrade from 2019 Essentials to Standard without having to reinstall?
Hi All,
I've placed a new OLP oder for one of my clients. It's being processed by the reseller still but I would really like to get cracking on building the Hyper-V VMs and preparing the the domain controller right away!
Can I download and use a Windows Server 2019 ISO downloaded from another customers OLP and then later successfully activate that copy of Windows Server 2019 with the newly ordered OLP keys once the order has been processed and assigned to me for access?
Can't find a definitive answer to this in the VLSC literature anywhere?
Also would setting up a DC and deploying servers not this new forest work as expected without any of the servers being activated right away?
As always thanks in advance...
durrie.
