One of my users was complaining of “slow vm performance over the network”, so I requested a few simple diags including a traceroute from his machine to the vm instead I got a traceroute from the VM to the VM. So I decided that clearly I was asking too much from the user and threw the following batch file together (I may rewrite it in powershell for fun later).
This is a function that allows you to clone a VM from a specified snapshot. The only way to do this in the UI would be to take a snapshot of the current state, revert to the one you wish to clone, clone, revert to latest snapshot and then delete latest snapshot. As you can see that is time consuming and takes numerous mouse clicks.
I recommend adding this function to your powershell profile so you always have access to it.
As always feel free to comment.
This little gem I wrote will listen to all interfaces on a computer for CDP packets. Once it has looped all the interfaces any packets it has captured are processed and added to WMI.
Using the attached SMS_DEF.mof we can extract that information and place it in SCCM. Anyone who knows what CDP is will see the benefit immediately. For the rest; CDP (Cisco Discovery Protocol), Cisco devices send out CDP packets every 60seconds each packet contains information about the port it was sent from and the sender. In a nutshell if my computer receives a packet then I can tell which switch I am connected to, what port on that switch and a few other bits and bobs about the switch. e.g. In a test environment I have a Cisco switch which connects to a Cisco IP phone which then connects to my computer, when exe runs I get two entries in WMI, one for the phone and one for the Switch.
The use case is that helpdesk may not know where a user is physically or where they are connected to the network and the user may be experiencing network issues, this would allow a helpdesk tech to locate the switchport the user is connected to and pass that info to the network team for troubleshooting saving both parties the hassle of tracing cables and also allowing reporting on where a user is plugging in over a period of time.
There is still a bit to be done for this but it does generally work.
Updated: 2013-11-20 – Added User submitted version of script to downloads.
I have tweaked my powershell script for the SCCM Dell/HP tags due to popular demand so that it can be run on a single machine using a list of service tags as the source and then will output to a CSV file. The source CSV can have any number of columns however it MUST have the following three for the script to work “Name,Vendor,Tag” in its default state. You also need to edit the $infile & $outfile variables as required.
Sorry to all those that have tried to contact me via the contact form, for some reason hotmail has been blocking emails from anyone not in my address book for what seems to be some time. I have no idea why or when they started this. I have changed the destination address for the contact form to another of my email accounts, so hopefully this has solved the problem. If you tried to contact me in the past and I have not replied it is most likely due to this. Please try again and I will respond, if you do not get a reponse please add a comment to this post so I know you have tried to contact me.
A while back I had a support case open with MS about some scripting in winPE. In order to debug the problem we wanted to see what variables were declared & what their values were. The support tech came up with the attachted script, I never got round to adding it to my scripts folder, so I ran it by opening a command shell in winPE (F8) then “net use Z: \\
This is the next evolution in the warranty info fight, Dell keep changing their site which is rather frustrating. I have re-written the Warranty Info Scripts in powershell as in my opinion the code is a lot cleaner and more manageable, I’ve tweaked the MOF edit required to read this.
One major change to the script is that I have added support for HP systems, now I must stress I only have one or two of these, both are out of warranty and only had base warranties so something may have been missed / may not work as expected. You can either fix it and let me know the changes you make or let me know, via the contact page, the tag of one of your systems and I will look at it when I get a chance.
If you use any other version of the script from my site you will need to update sms.mof as the reports have changed.
I am quite shameless so if you find this useful feel free to click on donate and well, donate. :D
What info do you get?