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.
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.
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!
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”.
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.
Configure this to include whatever you want your sender address to be, and your SMTP server, then click apply and you should get this.
Now, let go back and open up the SCOM Report Subscription again, and there we go!
I hope I’ve made your day, at least a little bit easier.
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 1: VMware-viclient-all-5.5.0-1618071.exe
Download vSphere Client 5.5: VMware-viclient-all-5.5.0-1281650.exe
This one is going to be short and sweet, I’ve been testing SMTP with and without encryption and wanted a good script for that.
Here are the lines that you’ll want to look at configuring:
- Line 5: “$smtpServer =”InsertYourSmtpServerHere”
- Line 12: Change the $false value to $true if you want to encrypt your SMTP with SSL
- Line 13: If you’re using a non-default SMTP port, change the “25” to whatever you’re using
- Line 15: Only change this if you need to enter credentials for authentication
- Line 18/19: Change these to who you want to say the email is from, and to whom it is being delivered.
- Line 21: Change this to whatever you want your email title to be
- Line 25: Change this to say whatever you want the body of the email to say
There are also some write-host’s in there to let you know the values that are being run and whether or not they were successful, which will print to the powershell console.
I came across this today and thought I’d share this helpful little wireshark capture filter. Based on wireshark’s documentation if you use
“ip.addr != 10.10.10.10” that should show you everything except for packets with the IP addrress 10.10.10.10. The problem is … it doesn’t work. It turns yellow like this, and doesn’t filter that IP.
The trick is to negate the whole statement, then it will work. Instead of doing “ip.addr!=10.10.10.10” run “!ip.addr==10.10.10.10”. Wireshark then is able to read it as NOT ip equal to, instead of IP is not equal to. Once you do that, you’re golden (well, green).
Simple enough, and it works with any statement — IE if you RDP into a machine and run a capture you should probably include “!tcp==3389” somewhere in your filter statement.
I hope I’ve made your day, at least a little bit easier!