Kazi

This appears to be a BIOS issue, not an SCCM issue. Your BIOS will not make Disk 1 the bootable disk when another disk is inserted because the other disk is recognized as Disk 0 - this is normal BIOS behavior. Check your BIOS settings and see if there are any manufacturer updates that will allow you to choose Disk 1 as your bootable hard drive.

OK – sorry for the delay in posting a solution. It’s been a busy morning so far. J What I noticed was that in my custom client settings, anytime I clicked on Hardware Inventory and then clicked the Set Classes button, the Hardware Inventory Classes window would open but nothing would populate in the window and I would get an error message that would crash the Configuration Manager (after a few clicks of OK). No matter how many times I tried to check the Hardware Inventory, it would end up crashing the Configuration Manager console (I apologize to everyone, I don’t have the exact error message that was popping up) and I’d have to open it again. The only client setting that I could get into and successfully view the Hardware Inventory was the Default Client Settings. What I did was I deleted all policies with the exception of the Default Client Settings and I recreated them. Once I recreated them, I checked to make sure I could get into the Hardware Inventory and click on Set Classes without getting an error message. The new client policies let me set hardware classes without an issue. I assigned them their priority and then I deployed them to the proper collections again. I allowed a few hours and I checked the report and BAM! There they were… so something was corrupted inside of the old client settings that I defined previously. Once I created the new ones and deployed them, SCCM started reporting correctly. I hope this helps anyone who might have this same issue.

Sorry, I had the entire solution typed up and when I clicked "Post" I got an error message and lost the whole thing... I planned on coming back and posting the solution in a bit after Monday morning decides to calm down.

I was able to resolve this issue. Thanks to everyone who took a look at this and to those who replied.

Unfortunately mine doesn't show Windows 8.1 - still trying to figure out what is wrong and why they aren't showing. Funny thing is if I go to DEVICES and right click on a Windows 8.1 computer and click PROPERTIES it shows "Operating System - Windows 8.1 Enterprise" and "Operating System Name and Version - Microsoft Windows NT Workstation 6.3" so it's somewhere between how SCCM is reporting devices and how the reporting tool is gathering that information. If I'm off base, please let me know.

How did you create the task sequence? Did you use the wizard or did you create you own?

How did you create your capture task sequence? Are you trying PXE boot the computer and run the TS or are you using any kind of media as a bootable device and then trying to capture that way?

I wish I could do that - but my manager wants it in SCCM Reporting. I'm trying to figure out why it isn't there.

Hello everyone, Reports in SCCM do not show the latest operating system that we are running (Windows 8.1). If I go to REPORTING - REPORTS - OPERATING SYSTEM and choose Computers with a specific operating system, my only choices are: Microsoft Windows 7 Enterprise Microsoft Windows 8 Enterprise Microsoft Windows Server 2008 R2 Datacenter Microsoft Windows Server 2008 R2 Standard Microsoft Windows Server 2012 Datacenter Microsoft Windows Server 2012 R2 Standard Microsoft Windows Server 2012 Standard Microsoft Windows XP Professional Microsoft® Windows® Server 2003 Standard x64 Edition Microsoft® Windows® Server 2003 Standard, Edition Microsoft® Windows Server® 2008 Standard Our desktop OS that we upgraded to is Windows 8.1 (we did test and deploy a few Windows 8 computers prior to the release of Windows 8.1). I also have some Server 2012 R2 Datacenter installs that are out there and the Server 2012 R2 Standard only shows 1 computer in the list but I have about 10. Does anyone know why SCCM Reporting would not show Windows 8.1 and Server 2012 R2 Datacenter? Also, I can't figure out why only 1 server shows up under the Server 2012 R2 Standard? The weird thing is, the server that shows up under Server 2012 R2 Standard was built a long time after any of our Windows 8.1 computers. I have a single server for SCCM with SQL 2012 SP1 on the same server. I'm thinking it's something to do with SQL but before I go poking around, I'd like to see if anyone has any information I could use. Thanks in advance. Kazi

Thanks Peter. What I did was I created his "own" update folder and I'm going to have him use that one when he creates a update - that way I will be able to watch and see if his folders disappear and mine do not.

He went into Software Updates and downloaded updates for Windows - when he selected what he wanted to download he clicked on Download which asked him if he had a deployment package already created or if he wanted to create a new one. He chose create new deployment package and for Package Source, he clicked on Browse and went out to \\SERVER\CM_DSL\UPDATES and when in there, he clicked on New Folder and created the folder "Workstation Update" then chose that folder and clicked OK and Next. That's how he saw the folders were gone again - because when he created the new folder he noticed none of the other ones were there. Does that make sense?

Yes - He said he didn't delete anything. He said he went in to create the new update and when SCCM asked him where to save the downloaded files, he went to the server\Updates folder and was going to create the folder on the fly. That's when he noticed the previous folders were missing.

Just an update on this - I thought I had this nipped in the bud by setting permissions on the Update folder because the folders were there last week since my last post in April 16... Then yesterday the other SCCM Admin created an update deployment and said the folders are gone again! Is there something in R2 that is "designed" to delete those folders in order to keep it clean? I *believe* I can still deploy the updates because they were copied to the DP - but I'm not certain. I'm going to set up a test computer and deploy to it using a Windows Update job where the folders are deleted to see what happens. I'll report back.

Have you tried the task sequence on different computers? I had an issue similar to this once (although I don't remember the error code) and the only way to fix it was to insert the operating system disk and format the hard drive. After I did that and tried again, it worked. This happened when we were running SP1, not R2 but it still might be worth a shot.

Just set up a collection based on "%wb%" and deploy the PowerShell to that collection - so have a PowerShell script that looks like this: Install-WindowsFeature -Name Web-Server -IncludeAllSubFeature -ComputerName Server1 Just add what feature you need and if you don't need all sub features, then don't include the -IncludeAllSubFeature. If you would like more of an explanation let me know in a PM.