SCVMM 2012 R2 Bare-Metal-Deployment not starting

Hey!
I have a W2K12 R2 Server with SCVMM 2012 R2 CU4 and enabled WDS-Role.
The Server ist already registered as a PXE-Server within SCVMM.
When I start a Bare-Metal-Deplyoment, it fails during DeepDiscovery, because it's not booting into the Bootimage using PXE.
I had to set DHCP-Options 66 (SCVMM-IP) and 67 (boot\x64\wdsnbp.com).
The VMM OSD Provider is installed. Below is the output of wdsutil /get-server /show:config I have also checked the path (D:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll) for the .dll
WDS PXE Providers:
Name: VMMOSDProvider
Path: D:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll
Order: 1
Critical: Yes
Name: WDSDCPXE
Path: C:\Windows\system32\wdsdcpxe.dll
Order: 2
Critical: No
Within WDS PXE is configured to respond only to knwon Clients (or not to any)
In the WDS-EventLog I Receive the following error:
The following client attempted to boot from PXE but was ignored because it is not recognized:
Hardware Address: 40-F2-E9-C3-71-74
IP: 192.168.222.5
Device ID: {2740D0D9-885B-11E4-AF74-40F2E9C37170}
ClientArchitecture: 1
Prestaged: false
The Device GUIDs are matching between VMM and the Device.
Do you havbe any further Ideas?
Kind Regards
jojo

Hi Sir,
As the title you posted , it is VMM bare-metal-deployment .
Please refer to following artiles for VMM bare-metal-deployment :
https://technet.microsoft.com/en-us/library/gg610658.aspx
http://borgamentes.blogspot.in/2013/09/bare-metal-deployment-with-vmm-2012-sp1.html
Hope it is helpful to you .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Similar Messages

SCVMM Bare Metal Deployment with SAN Boot

Can VMM assign "boot targets" to hosts while deploying them? Or do I have to do it manually before initiating VMM deployment? Specifically talking about PowerEdge M420. But also interested if it is possible in general?
The data above this text is pseudorandom, brace yourselves.

Hi Sir,
http://support.microsoft.com/kb/305547
This article shows the key point is we need to make the LUN works properly like a local disk , it also means that we need to prepare HBA driver within WinPE image before the deployment .
I have also read these blog regarding adding drivers for SCVMM Bare Metal Deployment:
http://www.thecloudbuilderblog.com/blog/2012/1/26/scvmm-2012-bare-metal-provisioning-adding-drivers-to-winpe.html
http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/installation-and-deployment/performing-bare-metal-installation-hyper-v-using-system-center-virtual-machine-manager-2012.html
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Bare-metal deployment to previously used host fails - removing host references.

I am running SCVMM 2012 R2 and setting up bare-metal deployment of Hyper-V hosts. I got it almost figured out but I am getting a failure when it tries to register the host with the error The fault reason was: 'Unexpected registration of physical
computer 4a310166-642f-e211-0050-05000000003a.' in the vmm log file vmmagentpe.exe.log. The error onscreen in PE is
Error: 803d0013. I have been using this server for my testing and have had a few other failures which are now resolved. All other tasks in the job complete except for
Wait for physical machine to reboot and customization to be finished.
This host was also registered in VMM as part of a manually built cluster before I started looking into bare-metal. I believe the problem is that there are probably references to this host in VMM.
Does anyone know where to look in the db or another method to remove anything related to this host?

I figured this out. It was rebooting to PXE instead of booting to the newly installed OS. once I reset the boot order to local disk it came up and ran mini-setup, domain join and all as expected.
-tim

Bare-metal deployment of non-hyper-v host possible?

Is it possible to use VMM 2012 R2 to perform a bare-metal deployment of a physical server which will not be a Hyper-V server? Just trying to find out if there's an opportunity to consolidate our build process to replace OSD or using the MDT. In this scenario
I'm willing to consider options that don't involve using the VMM/App Controller interface (i.e., calling the PowerShell cmdlets directly).
William Busby, PMP

Nope. not at this time.
VMM focuses on managing the fabric components that the VMs require.
You can build a Service Template that stands up an app server as a VM. But, it would be managed by VMM. So it really does not fit your ask.
You need to look into configurations and desired state configuration. At least that way you can define your end result and apply it to any machine. But you still have to automate the deployment of the OS somehow. Using WDS if you want to
go that route, or any of the 3rd party management layers.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Rename vNics during bare metal deployment

Hi all!
I am deploying a cluster of Hyper-V hosts with VMM, each host with two vSwitches. The first vSwitch is intend for guest VMs and the second for host management, heartbeat and live migration (all vNics). I have configured IP-pools for the three
vNics and technically it's all working like a charm. The issue I have concerns the actual day to day management in regards to monitoring which host has which IP. When running Get-SCIPAddress | Out-GridView it produces a list of all IPs "leased"
from VMM, but I find it hard to see which host has the actual address for the heartbeat and Live migration vNics when looking at the description column. For the bare metal deployed hosts it the description shows the vSwitch name plus an incremental number
and not the actual hostname of the host using that particular IP.
Example: For host1 it would read "HostSwitch5" for the LiveMigration IP and "HostSwitch6" for the heartbeat IP.
If you have a great number of hosts and all of them show the same description it gets pretty confusing.
The management vNic IP shows the hostname for the host in the description column and I'd really like the other vNics to show the same. Maybe this has something to do with this being the only vNic configured with a gateway and DNS or something?
Now, I could use the AssignedToID column but that only outputs the host's GUID which (at least for me) is not "human readable" :) So, I'd like to change the description field of each IP to read the actual hostname of the host using it. Is this
possible?

I specifically asked the product team about that.
And this has actually been the behavior all along. However, it was never my experience until after applying UR2.
And this is an experience vs. Product behavior thing. Somewhere in the process something changed with how the one is decided upon when vmm gets more than one match.
I am going to add this to my discussion with them.
Glad we have your issue resolved.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

Bare Metal Deployment - find-SCComputer reports wrong GUID

Hardware: IBM x3850, RSA version 1.42 (latest)
Bare metal deployment from the SCVMM GUI (2012R2) fails with error code 1001. Wrong SMBIOS GUID is reported by SCVMM.
Interestingly we´ve tried 3 different tools of which the first and second tool reports the correct GUID:
1st Tool is from Sourceforge called "ipmiuitl"
GUID = cda9bc20-d7e0-11e2-xxxx-xxxxxxxxxxxx
2nd Tool is from IBM called ASU or ASU64,
GUID: cda9bc20-d7e0-11e2-xxxx-xxxxxxxxxxxx
3rd Tool SCVMM Powershell Find-SCComputer
GUID: 20bca9cd-e0d7-e211-xxxx-xxxxxxxxxxxx
Seems like find-SCComputer reads the first three sections backwards.
Any thoughts?

Hey mate,
With respect to the deep discovery:
Are you able to check the WDS logs on your PXE server?? Are then any error events in there for the WDS server rejecting GUIDs or rather rejecting requests because of an unexpected GUID??
Regards,
adrian

After instaling the update for OS yesterday (saturday 7.10.2012) my macbook pro will not start. The instaling proses start but stopp after 2-3 minutes. I have started mayby 10 tims know but it stops every time. Help, its just a monts ago my iMac hard fail

After instaling the update for OS yesterday (saturday 7.10.2012) my macbook pro will not start. The instaling proses start but stopp after 2-3 minutes. I have started mayby 10 tims know but it stops every time. Help, its just a monts ago my iMac hard fail

Actually it sometimes gets a little further, the display will dim and the pointer will appear and then whoop it will turn off. if i do a verbose start up, it will finish all the steps, the white screen will appear and dim and then it will turn off.

Bare Metal Deployment

When Deploying a VHD through Bare Metal you end up with a C: that is 40 BG is size and a D: the size of the physical drive. Is there any way to change the size of the resulting C:
Is there any good documentation on this

The size of the "C:" drive is dependant on the size of the VHD(x) file you are deploying to the host.
You will always see the D drive and it will always show the entire size of the physical drive as it is indeed the physical drive that hosts the VHD(x) file (the C drive is the mounted VHDx file stored on the "D" physical drive).
If you want to see the C drive as using all of the available space the physical drive has, size it appropriately when creating it.
However... 50-60Gb should be sufficient for any deployment as it should only ever be the Base OS, plus Hyper-V component + drivers + Management tools/Agents. The physical drive needs enough space to store the expanded size of the VHD(x) file plus the Page
File (this is created outside of the VHD(x) file).
This also means that you can then use that VHD(x) file to deploy to any server with a physical drive bigger than say 60Gb rather than sizing the VHD(x) file at 200Gb and only being able to use it with servers with 200Gb+ physical drives.
This link might help you understand it more as it's a general Windows feature not VMM/Hyper-V:
http://technet.microsoft.com/en-us/library/hh825689.aspx
My System Center Blog

SCVMM 2012, Conntect via conosle does not work when logged in with specified credentials

Hi all
I have a problem with the SCVMM 2012 console. When I start the console I select the "Specify credentials" option and then I enter my admin credentials. Afterward the console opens
and everything works except the "Connect via Console" function.
When I try to connect to a VM I get the following message:
Virtual Machine Manager lost the connection to the virtual machine for one of the following reasons: Another connection was established to the console of this machine. The virtual machine has been shut down or put into the saved state. The user credentials
provided do not have the necessary privilege to connect (0x0003, 0x0300)
It seems that the Virtual Machine Viewer runs not under the admin credentials which I enter at the beginning and therefore the console cannot connect.
Has someone the same issue ? Is it by design that the console connection does not work with specified credentials or is a sort of a bug or error ?
Thx
J0fe

Being new to SCVMM, I've just come across this issue myself, though I came to a different (not necessarily better, but good enough for me) resolution.
I have a somewhat convoluted but not abnormal configuration where the SCVMM server lives in a separate untrusted forest to that which the Hyper-V Server hosts live.
As people have noted in this and other threads, the VirtualMachineViewer.exe process launches in the same security context with which you logged onto your pc. While the VmmAdminUI.exe process also runs in the same security context,
the network logon it issues makes use of the credentials provided at the SCVMM MMC's logon screen, which VirtualMachineViewer.exe does not.
I elected to use Credential Manager to resolve this issue.
In Credential Manager, I created a "Windows Credential" entry where the hostname matched the FQDN of the hostname that appears within SCVMM as the virtual host entry. Using an IP does not match if you've used an FQDN in the SCVMM
registration, and vice versa. If you used an IP for the host in SCVMM, then you need to supply that IP as the hostname in Credential Manager, and likewise if you used a FQDN.
This solution isn't perfect as it requires you to manage numerous Credential Manager entries (one per host), but that still appealed to me far more than one per guest. If I had a larger environment, I'd script the account configuration
given it only needs to happen once per host, rather than on an ongoing basis of once per guest as some of the above approaches would require.
I haven't tested the different combinations to verify the least permissions required. For the time being I've gone with the model of using a non-privileged domain user account (to avoid managing multiple identities and passwords)
which I added to the local Administrators group of each Hyper-V Server host. This stuck me as being a sound enough compromise between rigid security and ease-of-administration (given the per host arrangement in Credential Manager).
With the account correctly specified in Credential Manager, I'm able to move on past the 0x0003 error and successfully use the remote function.
If I was to point out an upside to this, it would be that this approach would allow me to remote Hyper-V servers in untrusted forests (including workgroups), which is something I couldn't do if the VirtualMachineViewer.exe process
did in fact use my SCVMM credentials alone. Ultimately, that's something you have to come to terms with yourself, though.
Cheers,
Lain
Thanks a bunch Lain, this helped! I'd still consider this a bug, however, and not a workable solution for a large number of servers/admins... But for now this does the trick, thanks!

SCOM 2012 Data Access Service could not start

Hello,
I have 3 SCOM 2012 servers. I got the error that the All Managament Server Pool is not available. Google search give me a lot of posts to add folder PoolManager at HKLM\System\CurrontControlSet\services\HealthService\Parameters with the DWORD keys PoolLeaseRequestPeriodSeconds
600 and PoolNetworkLatencySeconds 120. After restarting last SCOM server the Data Access Service could not run "Windows could not start the System Center Data Access Service. Error 1053: The service did not respond to the start or control request in a
timely fashion"
At Operations Manager Eventlog I see an error: "OpsMgr Management Configuration Service failed to communicate with System Center Data Access Service due the following exception: System.Runtime.Remoting.RemotingException: Unable to get ISdkService interface.
Please make sure local Sdk Service is running."
At System Eventlog I see an error: "A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect."
Why did it run on the both other servers and failes on the third one? What can I check?
Regards, Doreen

Hi,
According to my understanding, after editing the registry key value, two of three management servers work fine now, and the issue only occur to the third one. Whether all those servers are running with Windows server 2012?
I would like to suggest you re-check the service account for the data access service, maybe we can re-enter the account credential. Those three servers may use the same account for the service, make sure the account is not disabled and you enter in the right
password for it.
Here is a similar thread, please go through it for more details:
http://social.technet.microsoft.com/Forums/en-US/f2281934-513d-4b60-bb4b-34ae8a892ace/failed-to-open-the-console-and-system-center-data-access-service-wont-start-scom-2012?forum=operationsmanagergeneral
In addition, please also restart the third server and check the result, and I know that there is a similar error message in SCOM 2007:
http://blogs.technet.com/b/csstwplatform/archive/2012/01/02/scom-2007-r2-unable-to-open-the-scom-console-after-server-reboot-the-sdk-service-is-stopped.aspx
Regards,
Yan Li
Regards, Yan Li

Deployment not starting....

Hello all,
We are trying to deploy Flight List program in the Developer studio...
When we right click on "deploy new archive and run"
It only shows message upto Start Deployment ...
The process stops here nothing happenes... no log .
It does not ask SDM password. ( SDM is showing green in J2EE view)
Please let me know if anyone of you know about this...

HI Amit,
restart SDM and try once again

Bare metal deployment stuck at point 1.2.13

Hello everyone,
I got sccm2k12 R2 and am deploying a VHD file that has been syspreped.
Everything is going ok and the image is being deployed to the physical machine.
However, the physical machine being provisoned is prompting me for ctrl alt delete to sign in and the sccm server provisioning the server is hanging on step 1.2.13 0%
Does anyone know of why this is stuck?
I also did a reboot by singing into the physical machine but sccm just keeps hanging on step "1.2.13 wait for physical machine to reboot and customization to be finished"
Andre

Hi there,
Yes, my problem was DNS.
I had 2 domains in the same subnet.
Setup:
1 subnet like 192.168.1.0/24 with domain abc.local and dns server 192.168.1.1
My setup and my domain is andre.local with ip 192.168.1.100
As my sccm server is sccm.andre.local and the DNS server was 192.168.1.1 and I didn't had configured a conditional forward for the andre.local it couldn't resolve sccm.andre.local on the 192.168.1.1
So please make sure that your DNS server ( the dns that is given on pxe boot to the pysical to be provisioned server ) is able to verify your sccm server dns name.
Solution was to make a conditional forward for everything that has the andre.local to be directed to the 192.168.1.100
Andre

What is your preferred method of remote bare metal hyper-v 2012 server imaging

I need to remotely provision (image) 32 Dell 620 servers (they have iDRAC installed), I will have system center 2012. I was thinking PXE boot and place images on the servers. I know I can use the iDRAC to remote boot a virtual ISO file and install the OS
that way. I am looking for a better faster and more pre-configured OS way.
I am used to using Shadow Protect (ghost like product) and making and placing 0 and 1 disk images on servers, I would like to continue along that vein. But with added ability to PXE boot and image the server that way. I am looking into clonezilla and want
any thoughts of success or failures with server 2012 deployment.
I understand that you can use system center 2012 to deploy images to your bare metal servers (lots of moving parts and looks pretty complicated) and that it will then deploy a VHD image file to your server. I am assuming that means it will boot to the VHD
file (hyper-v light) . I have heard this slows down disk read\writes and can cause some issues.
Thoughts with clear instructions please. Only link me to a website if it helps you to not type so much.
Also looking into the DELL KACE server.
Can anyone tell me if I need system center only or if I need Configuration Manager to image servers??
[email protected] visit my blog stephanco.blogspot.com

You can use SCVMM 2012/2012R2 bare metal deployment
http://blogs.technet.com/b/cloudytom/archive/2012/01/02/scvmm-2012-bare-metal-deployment-checklist.aspx
Darshana Jayathilake

SCCM 2012: OSD to VHDX, deploy VHDX bare metal via TS?

Hi,
I wonder what your point of view is on the following scenario:
1.Deploy ts to vhdx
2.Deploy this vhdx to pc (bare metal) via another ts, this ts would then:
-wipe the disk
-make bootpartition
-add vdisk via bcdboot
It would give a lot of flexibility in terms of deployment speed (only 1 file to deploy, not that many reboots)backup (mount vhd to recover data),adding extra os, running clients vhd on hyperv host ...
Only issue would be how to add machine specific drivers.
Please advise.
J.
Jan Hoedt

Hello,
Only issue would be how to add machine specific drivers.
The answer is to this question. And in order to deploy VHD, you can follow this blog:
SCCM 2012 R2 – Create Virtual Hard Disk (VHD)

SCVMM 2012 SP1 (RTM) Deployment from VMM Console fails.

Error During a library refresh, or deployment from template - It all fails:
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server (MyServer).
Unknown error (0x80338105)
Recommended Action
1) Ensure that the Windows Remote Management (WS-Management) service is running on the server (myserver).
2) If the System Center Virtual Machine Manager service on your VMM management server is configured to run by using the machine account, ensure that there is not a group policy that does not allow adding machine accounts to a computer's Administrators group.
If there is, you can use one of the following workarounds:
- Disable the group policy in Active Directory Domain Services (AD DS)
- Modify the group policy to allow the VMM machine account in the Administrators group
- Move the machine account to its own organizational unit (OU) and block the group policy from being applied
- Reinstall the VMM management server and choose the option to run the System Center Virtual Machine Manager service by using a domain account, and re-add all of your virtual machines.
So, as soon as SCVMM 2012 Sp1 was released we decided that it was best to upgrade so we could utilise the new features of Server 2012 as a host.
The upgrade worked a treat. VM's deployed, Server 2012 worked. Anyway, a few days after deployment we start to see errors relating to WinRM and permissions (See end of the post). After a quick trace around we found some failed services, usually on a host
but sometimes it seemed to happen on the Library/Management server as well.
So, our setup is as follows:
Management/Library server = VMware VM, Server 2012 standard, 6 GB memory, 4 vCPU's
Hosts = HP DL360p G7, HP DL360 Gen8 (we have a few of these), Server 2012. We also have a DL380 G7 on Server 2008 R2 Enterprise that fails as well, so it seems the error isn't O/S specific (I'm picking a VMM issue).
So I have tried many resolutions and now none of them work.
We have no restrictions on group policy for the local admin, this can be set manually, and works for that matter.
WinRM is working and the listening port is 5985 (I can see it working and listening via a "netstat -an")
Also, I have ensured many many times that all of the required services are up and running (SCVMMAgent, VirtualDisk managerment, WinRM) and initially these where at fault and a simple restart of each service (or even a full start from dead) fixed
it - Now it all fails. Even a library refresh fails. And all while each of the services required are up and running.

So, I have now tried a reinstall of the management server & made some changes
1- Changed the service account during the install.
2 - Added the service account user to the local admins group of each host in question.
3 - Tried "winrm /qc" .which lets me know its already up and running and configured. Although I must admit, I'm not 100% sure how to use WinRM. From what I can read, this is like an express setup and ensures you are up, running and listening.
4 - Verified that WinRM is working of the right port (Listening ports dump below)
5 - Verified that I can connect to each port required for the SCVMM Management server.
BUT, it seems the error is still there and deployments still fail,
although the library refreshes correctly now.
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server ( Myserver).
Unknown error (0x80338105)
NETSTAT Listening ports dump.
PS C:\Users\nzadmin> netstat -an
Active Connections
Proto Local Address          Foreign Address        State
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8000           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8100           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8101           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8102           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8103           0.0.0.0:0              LISTENING
TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49170          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49201          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49211          0.0.0.0:0              LISTENING
TCP    127.0.0.1:57388        0.0.0.0:0              LISTENING
TCP    172.23.16.69:139       0.0.0.0:0              LISTENING

SCVMM 2012 R2 Bare-Metal-Deployment not starting

Similar Messages

Maybe you are looking for