SCCM 2007R2 - WDS/OS Deplyment.

[Dan_ATR]

I have tried to trouble shoot this for about a month now, and its really getting annoying. Other than SCCM2007 is the most poorly created software I have ever come across, I have more less got most things working other than getting the WDS/Operating System Deployment system working.

 

My problem is that after I have booted PXE (As in I can press F12 and download the boot file) It then comes up saying that "The windows boot configuration data file does not contain a valid OS entry." "Status code:0xc0000098" "File:\Boot\BCD"

 

Now, I can understand why this would be saying this, because WDS has no OS entry added but SCCM does have one added. I was under the impression that SCCM took control over WDS and there for no WDS configuration would need to be changed.

 

I have reinstalled WDS, I have also reinstalled SCCM2007 on a clean base two times and still I am unable to get this working. I was told you add everything in first like WSUS, WDS, updates etc.. before you install SCCM.

@Oaktech Has no idea either... probably because he is busy eating chocolates right now.

Edited November 13, 2013 by Dan_ATR

[Dan_ATR]

Also just adding, I have in DHCP;

066 Boot Server Host Name = (my ip address)

067 Bootfile Name = SMSBoot\x86\wdsnbp.com

 

I do not have 060 added and when I change 067 Bootfile Name from "Boot\x86\boot.com" to "SMSBoot\x86\wdsnbp.com" it then says PXE-T04: Access violation PXE-E36: Error received from TFTP Server. I have compared both folders and they are the same... double stumped.

[free780]

Have you distributed a boot image and deployed a task sequence? How come your not using sccm 2012?

[Gatt]

Have you distributed BOTH the x86 and x64 Boot Images?

 

Try removing the Images from your DP's completely and redistribute them.

Another option is to delete them entirely and recreate them from \\SCCMServer\SMS_XXX\OSD\boot\[x86 and x64] (Where XXX is your Site Code(

 

Check on \\WDSServer\REMINST that you have at least the SMSBoot and SMSIMages folders and they are populated:

(SMSBoot should contain you PXE files anf SMSImages should have the actual boot images from SCCM (eg XXX00004\XXX00004.wim, etc)

 

If none of these are present then your WDS may not be installed correctly.

SCCM 2007 is quite picky about WDS and doesn't like it if WDS was already installed - it really wants it installed but NOT configured.

 

I would strongly suggest upgrading to R3 at the very least if not 2012 R2 (Recommended!). and taking a look at Windows-Noob.com - they have some great guides on ensuring SCCM is correctly configured/

 

Also, this post on there might help as it looks like the same issue as your having. Configuring WDS for SCCM 2007 R3 - Configuration Manager 2007 - www.windows-noob.com

[Dan_ATR]

Have you distributed a boot image and deployed a task sequence? How come your not using sccm 2012?

 

Nope, not done this. I have no idea how to use the software to be honest with you. Im just using common sense and trile and error to use it. I did use SCCM2012 but I could not see where I can deploy any OS images etc... Which part of SCCM2012 do I need for this? We are currently on an RM network but have created a new domain and DC which we hope to move everything across to at some point and wish to use something like SCCM to manage the WSUS and OS deployment of things, users, groups etc..

 

Have you distributed BOTH the x86 and x64 Boot Images?

Try removing the Images from your DP's completely and redistribute them.

Another option is to delete them entirely and recreate them from \\SCCMServer\SMS_XXX\OSD\boot\[x86 and x64] (Where XXX is your Site Code(

 

I removed the two boot images in SCCM and added one back but no go.

 

Check on \\WDSServer\REMINST that you have at least the SMSBoot and SMSIMages folders and they are populated:

(SMSBoot should contain you PXE files anf SMSImages should have the actual boot images from SCCM (eg XXX00004\XXX00004.wim, etc)

 

If none of these are present then your WDS may not be installed correctly.

SCCM 2007 is quite picky about WDS and doesn't like it if WDS was already installed - it really wants it installed but NOT configured.

 

SMSBoot has the dir layout but only has bootmgfw.efi in the x86 dir. All other dir are empty which might well be my issue here. Or at least one of them.

 

I was told that WDS needs to be installed but not configured prior to SCCM installed which I did.

 

I would strongly suggest upgrading to R3 at the very least if not 2012 R2 (Recommended!). and taking a look at Windows-Noob.com - they have some great guides on ensuring SCCM is correctly configured/

 

I might try SCCM 2012 again in that case. Myself and @Oaktech have no idea how to use this stuff... need babe steps and a holding hand.... lol

 

Also, this post on there might help as it looks like the same issue as your having. Configuring WDS for SCCM 2007 R3 - Configuration Manager 2007 - www.windows-noob.com

 

Might take a look.. thanks

[Gatt]

Point to note:

 

You need to make sure that the x86 boot images is ALWAYS distributed - even if you are only using X64 images.

A PC will initially use the x86 boot image, and then switch to the x64 image accordingly.

 

Read through all the config guides on windows-noob and you'll get to where you need to be.

It took me 3-4 installs of SCCM before I became comfortable in using it - it is a duanting bit of software at first, but once you get it all configured and working then it'll be worth the blood, sweat and tears...

 

You are right about WDS - install the WDS Server Role, but do NOT configure it and let SCCM do that when you install the SCCM OSD Role.

(This isn't the case with 2012 btw, wher you shouldn't install WDS at all - SCCM does it all for you!)

[Dan_ATR]

Iv scraped SCCM 2007... now installing 2012

[Dan_ATR]

(This isn't the case with 2012 btw, wher you shouldn't install WDS at all - SCCM does it all for you!)

 

What about WSUS? Anything else I should uninstall??

[Gatt]

Same principle as WDS - install WSUS role, but do not configure it. Edited November 14, 2013 by Gatt

[Dan_ATR]

Sorry, I mean for SCCM 2012 does it install it too or do I need to install it? (ill leave it where it is in that case)

[Gatt]

Just seen you're installing 2012 so just to clarify:

 

WDS - This should get isntalled by SCCM when you install the OSD roles

WSUS - Install WSUS bot don't configure it, then install the SUP roles

[Dan_ATR]

Now im lost... I keep getting this message up when trying to connect to the DB. Iv followed everything according to the windows-n00bs how to.

 

[Gatt]

Make sure the username you are using to install SCCM has the rights to connect and create a database on the SQL Server through SQL Management Studio

it's either db_owner or db_creator?

Rerun setup

[Dan_ATR]

nope... still not working...

[Gatt]

Are you using the default instance? IF so leave the second field blank

[Dan_ATR]

no, I make up my own instance... this all worked fine for SCCM2007.

 

I have Server 2008 R2 with SQL 2008 R2 Standard and a secondary DC with Server 2008 R2 with SCCM 2012.

[Dan_ATR]

Help...

 

Right, iv scanned the net for loads of ideas why this might not be picking up the SQL database and its really getting on my tomato source.

 

I have installed now SQL 2008 Standard R2 SP2 CU8

 

I have domain/SMSAdmin, domain/Administrator, built-in/Administrators Group added to the SQL login access.

 

I have added dbcreator, sysadmin and db_owner to all of these users/groups for the dbs and server roles. All have Grant to connect to the database engine and login is enabled.

 

Named pipes, Shared Memory, TCP/IP are all enabled in the Configuration manager.

 

I am using ports 4022 as standard and the Instance name is leafsqlserver.

 

collation is SQL_Latin1_General_CP1_CI_AS.

 

Just to let everyone know too, the SQL server is another VMServer and the DC2 with SCM2012 is another VMServer both on the same box. SCCM2007 worked fine with the SQL connection.

 

>.<

Edited November 18, 2013 by Dan_ATR

[Dan_ATR]

Stand-alone primary site (SQL Server installed Locally)

 

Up to 100,000 clients

SQL Server is installed on the site server computer

 

Are you taking me for a giraffe? GRRRAAAAA!!!!!!!

[Gatt]

I'm pretty sure my SCCM is a stand-alone primary (that is - I don't have a CAS server) and a remote SQL Server

Though I use the default instance of SQL

 

Also you seen this link: IT notes: SCCM 2012 Installation Guide

 

They seem to be installing it similar your yourself

[Dan_ATR]

Nope... something is really fishy here... Even the firewall is off..

[Dan_ATR]

GRRRRRRRRR..... Its fine if you type in the default MySQLInstance... dam Microsoft...:smash::smash:

[Dan_ATR]

Back to square one.

 

With SCCM2012 what do I need to add to DHCP manually as its not in the how to on windows-n00bs.

 

60? 67?

[Gatt]

If you are referring to what I think you are then in the DHCP Console make sure Options 66 & 67 are set as shown

(Providing your DHCP is on a different server to WDS.. Option 60 is only needed if WDS and DHCP are on the same server IIRC...)

 

[Dan_ATR]

WDS and DHCP and AD and SCCM2012 are all on the same box.

 

So in that case i need option 60 right? But they would surly go off to the wrong boot file?

[Gatt]

Yeah you'll need option 60 then... This might help: PXE Boot using DHCP options

 

Not sure what you mean by "Wrong boot file" though?

If you mean the file in Option 67 - then I would recommend this be x86 and you disitribute x86 and x64 Boot images in SCCM otherwise you will get a load of issues with x86 and x64 based images not booting correctly - See: http://www.edugeek.net/forums/o-s-deployment/94602-pxe-boot.html