I’m still having a few teething issues. I booted up a physical PXE client this morning and had that strange error from a previous post, so I assumed it might be a PXE firmware issue or something. PXE booted my laptop fine, then booted the same client and that was fine too. ?
Also, I couldn’t figure out why my work PC (Hyper-V) wasn’t really getting the SCCM agent installed properly. Looks like I’d forgotten to configure Administration > Site Configurations > Sites > sitename > Client Installation settings > Client Push Settings. Also, there was no FQDN under Administration > Site Configuration > Site system Properties, made both these changes and it all started working fine.
I’ve kept getting the following error repeatedly, which is annoying because I deliberately rebuilt my test CM box in order to get rid of it (no pun intended). What was happening was that I’d create my test Hyper-V VM, remove the built in NIC and add the legacy NIC (for PXE) then boot the machine up. What happened next is (roughly) outlined in the following screen shots:
I say roughly, irritatingly I forgot to screenshot my equivalent of the second picture, so I “borrowed” image 2 from http://adventuresinosd.blogspot.co.uk/2011/03/troubleshooting-pxe-in-sccm-osd-part-3.html (the error I was getting wasn’t identical, but near enough).
Anyway, given this was a brand-new SCCM server I thought there must be something obvious to make this go away. I vaguely remembered something about anonymous access to the distribution point (possibly from www.windows-noob.com). So I went to Administration > Distribution Points, right clicked my sole (test) DP and chose properties. Ticked the “Allow clients to connect anonymously” tick-box and that did it- all of a sudden PXE is working. What’s weird is that PXE still works absolutely fine even after I’ve un-ticked the same box… no idea why but I don’t care, it works (this is the reason I had to use image 2 as I could no longer re-create the error I was getting to screenshot it).
3 weeks in or so, I’m getting to grips with System Center 2012 SP1 (on Windows Server 2012) but it’s been a right pain. Been through 3 complete re-installs, one of them due to a faulty Hyper-V machine.
Anyway, I thought I’d share some handy tips just for getting it installed… I should point out that these are for a test installation- for example, below I install the whole of IIS even though this probably isn’t needed, I just wanted to get the whole thing working (which is why I installed SQL in its entirety too). All the below were installed with evaluation licenses.
- Install Windows Server 2012;
- Join your domain;
- run the following PowerShell commands:
- install-windowsfeature net-framework-features -includeallsubfeature -source:D:\sources\sxs;
- install-windowsfeature rdc -includeallsubfeature -source:D:\Sources\sxs;
- install-windowsfeature web-server -includeallsubfeature -source:D:\Sources\sxs;
- install-windowsfeature updateservices-services -source:D:\Sources\sxs; //deliberately doesn’t include -includeallsubfeature
- install-windowsfeature updateservices-db -source:D:\Sources\sxs;
- install-windowsfeature bits -includeallsubfeature -source:D:\Sources\sxs;
- Now install SQL (2012 SP1), remembering to set the Database Engine collation to SQL_Latin1_General_CP1_CI_AS;
- Also, set the “SQL Server Database Engine” user to a domain user, NOT a local user or NTAuthority\SYSTEM etc;
- Now patch Windows as fully as possible. My test box is reporting needing 89 updates, it can do the first 65 in the first round (although we are quite specific about what WSUS patches so you might have a different number of updates);
- Don’t stop patching via Windows Updates until there are no more updates! I think this might have broken install 2 of SCCM…
- Install elements 2,3 & 4 of the Windows Assessment and deployment toolkit (http://www.microsoft.com/en-gb/download/confirmation.aspx?id=30652)- so that’s Deployment Tools, WinPE and UMTS
- You’ll still get 4 warnings- Schema Extensions, AD Publishing, SQL Memory and SQL Processor. However, at least you can now install SCCM.
- Install SCCM 2012 SP1 CU2 from http://support.microsoft.com/kb/2780664 (if needed)
- Run: C:\Program Files\Update Services\Tools>wsusutil postinstall SQL_INSTANCE_NAME=xxxx //connects WSUS up to a remote SQL DB (okay, even though mine is on same box- it’s different to a WID database)
To actually start configuring and using it, you need to visit http://www.windows-noob.com/forums/index.php?app=portal…