Month: July 2015

Powershell command to show names of all machines in SCOM

Posted on

Reading Time: < 1 minute

Simple one-liner, very helpful though!

Import-Module OperationsManager; Get-SCOMGroup -DisplayName “All Windows Computers” | Get-SCOMClassInstance | sort DisplayName | FT DisplayName

 

This will output just the names of all machines in the “All Windows Computers” group, you can change that name to output the machine names of any other group as well.

Server 2012 R2 “does not have a network adapter available to create a virtual switch” when configuring VDI

Posted on

Reading Time: 2 minutes

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”

fail1

 

Taking a quick look here, I do have a vSwitch. Why is it complaining?

vSwitches

 

 

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.

 

no-vSwitch

 

 

All gone, now try the installer again.

 

done

 

 

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.

Thanks!

SCCM Collection Query for all Workgroup Machines

Posted on

Reading Time: < 1 minute

Nothing too special about this post, just a query statement. Use this query in an SCCM collection and it will give you all WORKGROUP machines.

 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceDomainORWorkgroup = “WORKGROUP”

 

There ya go! Hope I’ve made your day, at least a little bit easier.

SCCM Client Logs for Software Update Troubleshooting

Posted on

Reading Time: < 1 minute

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.

  • UpdatesDeployment.log 
    • 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.
  • UpdatesHandler.log
    • Provides information about software update compliance scanning and about the download and installation of software updates on the client.
  • ScanAgent.log
    • Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
  • WUAHandler.log
    • Provides information about when the Windows Update Agent on the client searches for software updates.
  • UpdatesStore.log
    • 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!

Thanks!

 

No email option in SCOM 2012 report subscription

Posted on

Reading Time: 2 minutes

So this is the issue — you’re going to subscribe to a report in SCOM and the only options are “Windows File Share” and “Null Delivery Provider”.

NoEmailOption

 

Well that’s a problem…we want these reports emailed. This error typically occurs when a SQL Migration is done, the reporting role is migrated, or on new installs. So go open up SQL Server Reporting Services Configuration Manager, and go to the “email settings” tab on the side. Notice there’s no data in there.

SSRS-Email

 

Configure this to include whatever you want your sender address to be, and your SMTP server, then click apply and you should get this.

Results

 

Now, let go back and open up the SCOM Report Subscription again, and there we go!

 

EmailOption-yes

 

 

I hope I’ve made your day, at least a little bit easier.

 

Thanks!

vSphere 5.5 Client Download

Posted on

Reading Time: < 1 minute

I had to find the vSphere 5.5 client today and I have to say — it wasn’t very easy. In light of that, I’ll just leave the links here for everyone.

 

Download vSphere Client 5.5 Update 2: VMware-viclient-all-5.5.0-1993072.exe

Download vSphere Client 5.5 Update 1b: VMware-viclient-all-5.5.0-1880841.exe

Download vSphere Client 5.5 Update 1VMware-viclient-all-5.5.0-1618071.exe

Download vSphere Client 5.5: VMware-viclient-all-5.5.0-1281650.exe