I’m the kind of guy that ALWAYS has task manager open. I’m serious, ask anyone I work with — I sometimes even have a whole screen for Task Manager and Resource Monitor (Maybe that’s why I like SCOM so much?). Though, I’ve noticed a couple of times on Windows 8, Windows 8.1, Server 2012, Server 2012 R2 that when I open task manager the stats just freeze. The system is fine, everything is normal but the stats just freeze — like this.
They never do anything else, and just stay at that initial opening mark. So frustrating! I’ve SFC’d, I’ve rebuilt my performance library, I’ve copied new bits for taskmgr.exe, everything! It turns out for some reason sometimes the view speed gets set to pause. I never would have though of that, but somehow it just happens (though, I’ve never seen it happen in any OS earlier than Windows 8/Server 2012).
Here’s how you fix it. Go into View –> Update speed and notice it’s set to pause. So strange.
Go ahead and set it to normal and you’re back in business!
I hope I’ve made your day, at least a little bit easier.
Server 2012 R2 “does not have a network adapter available to create a virtual switch” when configuring VDI
I recently ran into this issue when doing an all-in-one VDI install, on top of a server that had been used for other things in the past. The “quick start” VDI option is supposed to essentially do everything for you, but I ran into this issue.
“The Server does not have a network adapter available to create a virtual switch”
Taking a quick look here, I do have a vSwitch. Why is it complaining?
It turns out that the installer isn’t actually complaining about the fact that there is no vSwitch, it’s complaining that there IS a vSwitch. It needs it to be a “blank slate” so it can manage it and do it’s thing. I’m not a fan of this, because I intend to manage my VDI environment using SCVMM, and the VDI component itself won’t have a whole lot to say about it. Nevertheless, this is how you get past this. Delete any vSwitches.
All gone, now try the installer again.
There we go, now we’re off onto the next step without any errors. Have fun!
I hope I’ve made your day, at least a little bit easier.
We all know SCCM can be your best friend, and your worst nightmare. Today I had to compile a list of client logs to check for a friend of mine, and thought I’d share. These should get you 95% of the way on your troubleshooting (from the client side anyways). Remember to always use CMTrace as your SCCM log viewer, it just makes your life easier.
All of these listed directly below, should be located in C:\Windows\CCM\logs on your client.
- Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
- Provides information about software update compliance scanning and about the download and installation of software updates on the client.
- Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
- Provides information about when the Windows Update Agent on the client searches for software updates.
- Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
You can also reference C:\Windows\WindowsUpdate.log which is a windows native log and not to SCCM, but is updated with actions taken by SCCM in regards to updates.
I hope this has made your day, at least a little bit easier!
Something that I’ve noticed not a lot people know, is how to get your disk performance to show up on a server’s task manager. Yes, yes, I know. With the new Microsoft model you shouldn’t be RDP’ing to servers anyways — but I still get asked how to do this. For some reason they have this by default on Windows 8, but not enabled on Servers. So here’s the one command you need to fix that.
1) The problem, no disk portion on task manager. 😦
2) Run the following command to enable it.
This enables the physical and logical disk performance counters.
3) Close and re-open task manager.
There ya go!
I hope I’ve made your day at least a little bit easier.
As I went to upgrade an evaluation version of System Center Configuration Manager 2012 to a full version, I noticed unlike Operations Manager — you have to do this through the setup/install interface. Upon first search people were saying just run the setup again and choose “Perform site maintenance or reset the site”, though it was greyed out. Here’s the quick tip to remedy that.
Here, I’m just running the setup again and choosing Install, and the option is greyed out to perform site maintenance.
So here’s what you do instead. Close the setup window, and go open Programs and Features in your Control Panel. Find “Microsoft System Center 2012 Configuration Manager Primary Site Setup” (this may be different if the top of your hierarchy is a CAS), and click “Uninstall/Change”.
Then, there it is — not greyed out!
Click next and you’re able to do what you need to do.
At this point you can do a few things.
- Reset your site with no configuration changes
- Modify SQL Server Configuration
- Modify SMS Provider Configuration
- Modify Language Configuration
- Upgrade Evaluation Edition to a Licensed Edition
I just needed to upgrade my site to a licensed edition, and this worked like a charm.
I hope I’ve made your day at least a little easier!
I know, I know — we shouldn’t use this on servers. Sometimes though, in the right environment and for the right reasons, it can be useful (and you don’t have to install something like ccleaner).
This process is honestly, really easy — the files are already on your system, they just need to be put in the right place. Take these lines below and either run them one at a time with an administrative command prompt or put them in a batch file and run all at once.
Server 2008 R2 x64:
copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe C:\Windows\System32
copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui C:\Windows\System32\en-US
These three lines will copy the needed files from your sxs folder and put them in your system32 which will allow you to call “cleanmgr.exe” from the command line.
I hope this makes your day at least a little bit easier!
I did a few new SCOM 2012 installs recently and noticed that after pushing the agent to the DCs, they showed up grayed out in Ops Manager. Here’s a quick tip on how to fix that.
Logon to the DC(s), and with an administrative comand prompt run the HSLockdown tool, and add the local system account to the allowed group.
C:\Program Files\System Center Operations Manager\Agent:
*NOTE* In newer version, this is now stored in “C:\Program Files\Microsoft Monitoring Agent\Agent”
Run the command “HSLockdown /L” to show what accounts are being allowed or denied. In this case, my local system isn’t even populated.
Now run the HSLockdown tool again with the add switch to allow local system.
“HSLockdown /A “NT AUTHORITY\SYSTEM”
Restart the agent with “net stop heathservice && net start healthservice” and give it 5 minutes or so then it should be all green in your dashboard.
Hope this made your day at least a little easier!