SharePoint admins occasionally have write PowerShell scripts to regularly extract some type of summary data from the SharePoint farm and then write that out to a file, usually in CSV format since PowerShell handles those so well. This is great for admins because we can just log onto the box and open the file to read the data, but what about the rest of the SharePoint team that also needs that data? Click to read the full post
As a SharePoint administrator, I end up either writing a lot of PowerShell scripts or copying existing scripts and modifying them to fit a new need. With all of these scripts comes the need to share them with other admins outside of the command line and in such a way that allows them to be easily Click to read the full post
When you work with SharePoint, you end up working a lot with both GUIDs and with PowerShell. Strangely enough, the two together don’t seem to be needed very much but eventually their paths cross. GUIDs in PowerShell are amazingly simple to create but the web is chock full of misinformation and insanely complicated suggestions. I’ve even seen some folks recommend passing parameters to New-Object!
So, just for the sake of clarity, here is how to create GUIDs in PowerShell. It really doesn’t get much simpler than this!
# Create an empty GUID $Id = [GUID]::Empty # Create a new GUID $Id = [GUID]::NewGuid() # Create a GUID with a value $Id = [GUID]("b2e92f11-7f65-41d1-acec-ba051b418bdf")
There’s nothing to it but some people choose to make this so complicated.
Update – 5/31/13 – I discovered a way to make it even simpler!