Could Not Contact Primary Server
We are running W2K8 R2, and had successfully started running DHCP. But, because of a need to remote boot a new machine we needed to add Active Directory to the server. After adding Active Directory our DHCP server would not run, saying that it first needs to be authorized. However, there is no option (either under the Action menu or when right-clicking on the DHCP server) to authorize. We thought that maybe the problem was caused by DHCP being on prior to Active directory, but even after removing DHCP and then adding it back we get the same problem. Can anyone help on this? Unfortunately, nothing was actually resolved from what we originally needed to do.
To resolve the DHCP issue we had to remove all relevant services and re-add them, losing all user accounts at the same time, so we almost had to start from scratch. And, the creating a terminal is apparently not possible with Windows Server, so we are back to just using an XP machine and logging in with RDP, which is exactly what we were trying to change. I do appreciate the help that everyone tried to give, but ultimately we just went around in a big circle and have ended up back where we started. These are the exact same instructions that I followed, so here is the issue that we hit: The DHCP server that was installed prior to Active Directory showed as not authorized. There was no place for us to select 'authorize', so we removed the DHCP role. When we rebooted and tried to add the DHCP role we received two errors at the end.
The first error stated that there may be a conflict on the scope, so I am guessing that, even though we had removed the DHCP service, somewhere it still had the scope listed. The second said that the attempt to configure DHCP failed with error 0x80074E66. The DHCP service could not contact Active Directory. We just tried removing the DHCP service and re-adding it, but entered a different range on the scope.
We still got the second error above. Any thoughts? The first error is: Attempt to configure DHCP server failed with error code 0x80074E54. The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the subnet address and mask of an existing scope. As mentioned, when we tried installing DHCP with a different address range (instead of.100.199 as we originally had set up, we tried.10.99) we did not get this error, but still received the error noted in the previous post (code 0x80074E66).
Not pretty, but by removing DHCP, Active Directory, and DNS (which removed user accounts, as well, but fortunately there were only a couple and they ran just a couple of installed programs), and then starting from scratch, we were able to get DHCP working under Active Directory. Now we just have to rebuild the couple of user accounts. Quite a nightmare, but I assume it had something to do with DHCP being installed and active ahead of adding Active Directory, as we did everything the same after complete removal, just in a different order. I am feeling kind of stupid now. I did change the server ip address, and just never thought of the implications on port forwarding. Maybe I need to take a break from this to let my brain catch up to all that I have done. I think that the only remaining issue is remote booting via WDS.
Should I ask that here (it is still to do with the network infrastructure), or start a new thread? If I can ask here- is there anything to set up (TFTP) to tell the remote computer where to find the boot information? The remote computer is getting an address from the server, but the PXE boot is aborting. Also, can a 32-bit machine be booted remotely from a 64-bit server? We have only one computer here that can be set up to LAN boot. Even my computer from home is not able to LAN boot, so I cannot bring it in to test. But, the computer that is supposed to boot over LAN is getting an ip address from the server, and it is downloading a file from WDS.
It then asks for the user to press F12 in order to boot, and either the computer is not accepting our input or there is some other reason that it is aborting the boot. I read somewhere that it is possible to change the settings so that there is no user input required, so I would like to try that. I guess my two questions are: 1- Is there anything that we need to set up beyond Active Directory, DNS, DHCP, and WDS for the server to allow a computer to boot remotely? Does WDS take care of telling the remote computer where to find the necessary files to boot up? I assume that it does, as a file does get downloaded from WDS when we try to boot remotely. 2- Will a 32-bit computer be able to boot remotely from a 64-bit server?
I assume that it can, but you know what they say about assuming.
Hello to all. I have Server 2012 with Hyper-V installed and RDS Services. I am trying to create a collection of pooled or personal virtual machines. Both choices give me the same error: Failed:the provisioned virtual machine could not connect to its primary domain Only the first virtual machine is created but with this error. The communication with the Domain is fine because I tried all tests like pinging etc, and during the setup of the collection the Domain is found without issues. The Virtual Machine acting as a Template has Windows 8 installed and 'syspreped'. Open to suggestions.
Thank you in advance. I solved the problem but I'm not exactly sure what solved it. I do think it was related to two things: 1) DHCP 2) Virtual switches. I had originally setup my sandbox with static IPs but went back and setup an integrated dhcp server.
It's also serving IPV6 addresses. I also had to correct a problem with the virtual switches. What I did was first allow the remote desktop service install wizard to install the first virtual switch. Which it did. You should have a virtual switch named RDS after this wizard.
It apparently is a different breed of virtual switch. But I also had to create two more virtual switches. One switch for internal. The other other is external and linked to a physical port. And then added two additional network adapters to my vm template, and linked them to these virtual switches. Your vm client will have three virtual switches attached to it. Internal, external and RDS.
Here's my short recipe to cook virtual desktops in sandbox: 1) Establish domain controller with dns and dhcp configured correctly. With IPV6 support. 2) Install HyperV, do nothing else.
3) Install Remote Desktop services. I'm going VM and not session but I think it works the same. There's a switch in this wizard to 'create a virtual switch'. Make sure you select that. And verify the switch in HyperV.
4) Create internal and external virtual switches in Hyper V 5) Create a vm template. Make sure your vm is connected to the domain and getting addresses from dhcp, before sysprep. 6) sysprep and generalize 6) create collection The create collection wizard was taking about two hours to tell me the domain contact error. When it finally worked, the create collection wizard took about 15 minutes to create a desktop. Hope this helps. Hi, Do you use VMM 2012 SP1 beta in your environment as well? (there is another step to do if got this) To add-on, a) Make sure your VM can get IP from DHCP and able to contact the DHCP & AD b) On Hyper-V Host, just install roles without create a virtual switch.
C) On your existing RDS Deployment, add Virtualization Host and point to (b) server. Remember to tick create a new virtual switch and it will create a virtual switch name 'RDS Virtual'- External Switch. D) Your VM template (win 7, Win 8), do not need to join to domain. Workgroup will work as well. These VM template bind to RDS Virtual Switch. Before sysprep, make sure can get ip from DHCP Server.
If can get ip and ping to DC, then sysprep & generalize it e) Create collection and point to (d) VM Template. Lai (My blog:- http://www.ms4u.info). HiFailed:the provisioned virtual machine could not connect to its primary domain How you receive such error message, what kind of operation?
Have you tried to unjoin the computer from domain then rejoin it? Please try to rejoin the computer to domain and give us feedback, provide us more information for further troubleshooting. For more information please refer to following MS article: Windows 7 or Windows Server 2008 R2 domain join displays error How Domain Controllers Are Located in Windows Lawrence TechNet Community Support. I solved the problem but I'm not exactly sure what solved it. I do think it was related to two things: 1) DHCP 2) Virtual switches. I had originally setup my sandbox with static IPs but went back and setup an integrated dhcp server. It's also serving IPV6 addresses.
I also had to correct a problem with the virtual switches. What I did was first allow the remote desktop service install wizard to install the first virtual switch.
Which it did. You should have a virtual switch named RDS after this wizard. It apparently is a different breed of virtual switch. But I also had to create two more virtual switches.
One switch for internal. The other other is external and linked to a physical port. And then added two additional network adapters to my vm template, and linked them to these virtual switches. Your vm client will have three virtual switches attached to it. Internal, external and RDS. Here's my short recipe to cook virtual desktops in sandbox: 1) Establish domain controller with dns and dhcp configured correctly.
With IPV6 support. 2) Install HyperV, do nothing else. 3) Install Remote Desktop services. I'm going VM and not session but I think it works the same. There's a switch in this wizard to 'create a virtual switch'.
Make sure you select that. And verify the switch in HyperV. 4) Create internal and external virtual switches in Hyper V 5) Create a vm template. Make sure your vm is connected to the domain and getting addresses from dhcp, before sysprep. 6) sysprep and generalize 6) create collection The create collection wizard was taking about two hours to tell me the domain contact error.
When it finally worked, the create collection wizard took about 15 minutes to create a desktop. Hope this helps. Hi, Do you use VMM 2012 SP1 beta in your environment as well? (there is another step to do if got this) To add-on, a) Make sure your VM can get IP from DHCP and able to contact the DHCP & AD b) On Hyper-V Host, just install roles without create a virtual switch. C) On your existing RDS Deployment, add Virtualization Host and point to (b) server. Remember to tick create a new virtual switch and it will create a virtual switch name 'RDS Virtual'- External Switch. D) Your VM template (win 7, Win 8), do not need to join to domain.
Workgroup will work as well. These VM template bind to RDS Virtual Switch. Before sysprep, make sure can get ip from DHCP Server. If can get ip and ping to DC, then sysprep & generalize it e) Create collection and point to (d) VM Template. Lai (My blog:- http://www.ms4u.info). I have the same issue my scenario is below.
'The provisioned virtual machine failed to connect to its primary domain' I will explain my environment here. I have a ESXi5.5 and managed by vCenter. I have created a VM guest with 25GB HDD, 8GB MEM and CPU Hyper-VT is enabled also added the parameters below parameters for enabling hypervisor provisioning from VM. Hypervisor.cpuid.v0 = “FALSE” mce.enable = “TRUE” vhv.enable = “true” I have installed Windows server 2012 R2 in VM guest and installed the RDS Virtual Desktop Infrastructure (VDI). I can able to get the DHCP address via external virtual switch. All the services are running very fine. I have created guest template windows 8.1 and sysprep ed.
Sophos Could Not Contact Primary Server
When I create Virtual desktop Collection I am getting the below error. 'The provisioned virtual machine failed to connect to its primary domain' I have tried to create vSwitch external and mapped to the guest template. Here I can able to get the DHCP address from externally, but I can't able to ping the DHCP or Domain controller or any other systems on external. Could you please someone to help me to resolve the issue. My requirement is to setup the Windows server 2012 R2 hypervisor in VMware VM and provide the VDI. You can send mail to my ID as well psn94@yahoo.com.
Advance thanks.