Jeramy Thompson

So I was interested in getting OSX running my my T520. I had looked into this about a year ago with no luck, but now there is a great write up for it by the guys over at insanelymac.com on how to do this. After doing my own research to get the required parts , software etc I now have a core i7 , 16GB (ill explain later) , and a 250GB SSD that makes OSX scream on this awesome piece of hardware. So to get started the first thing you are going to need is a whitelist bios patch for the Bios and can be found here: https://www.bios-mods.com/forum/Thread-REQUEST-Whitelist-Request-ThinkPad-T520-v1-43-8auj24us-exe Get the 1.44 versoin and flash your bios per the readme included, once its flashed install a OSX compatible WiFi card. Lenovo locks their laptops to intel only WiFi cards. Unfortunately there is little to no support for these on OSX so the best thing to do is replace it with a compatible card. These can be found on ebay for about $5. In my case I purchased a used Ather

VMware Horizon Access Point - Dynamic IP update powershell script. Some of us do not have labs at work, a tend to like to test things out before deploying them into production. Since i have a dynamic IP i wrote this powershell script to update my VMware Horizon Access Point every day. Enjoy To run my power shell script, since its not sighned , you have to allow power shell to run unsigned scripts run to following to allow it to run open power shell as administrator Set-ExecutionPolicy Unrestricted Update the following variables: Find this line: $pwd = ConvertTo-SecureString "P@$$w0Rd!" -AsPlainText -Force replace P@$$w0Rd! with your actual password for the access point Next find this line: $cred = New-Object Management.Automation.PSCredential ('admin', $pwd) replace 'admin' with the user you setup during install lastly find $proxyDestinationUrl = "cs.home.lab" replace cs.home.lab with the internal DNS of your home lab That is

I have created an Updated version 2.0, Please go Here for more info: VMware Horizon Access Point GUI power shell script: I wrote this script as an easy way update your VMware Horizon Access Point with power shell 3 or later.Enjoy Created a Video to show how easy this is: https://www.youtube.com/watch?v=-_byc3JxNew To run my power shell script, since its not sighned , you have to allow power shell to run unsigned scripts run to following to allow it to run open power shell as administrator Set-ExecutionPolicy Unrestricted Fill these out. ProxyDestination URL = your connection server ProxyDestinationURLThumbprint  = cert thumbprint, if you just put * its accepts all PCoIP Enabled: check this box if your using PCoIP PCoIP External URL = externally accessible IP for your access point Tunneling Enabled = check this box Tunnel external URL = externally accessable url for your access point, or IP VMware Access Point IP = VMware Access Point IP VMware Access Point Us

One of the issues we have to monitoring disk usage on our home directories. I needed a way to monitor who was using the most space, and to find out quickly who had used the most space most recently. So to start out i have created a simple powershell script to get the entire home directory size, and put that information into a SQL database. First i get a listing of all folders in the folder containing the home directories then for each Folder, i get the total size, and send that info to SQL Tables are setup [Name],[MB_Used],[Date]  , the date field is auto popluated dir D:\homeDirs | ForEach-Object { $colItems = (Get-ChildItem Z:\HOME\$_ -recurse | Measure-Object -property length -sum) $DasName = $_ $DasSize = "{0:N2}" -f ($colItems.sum / 1MB) $SQLServer = "SQLSERVER" $SQLDBName = "DATABASE" $SqlQuery = "insert into dbo.TABLENAME ([Name],[MB_Used]) Values ('$DasName','$DasSize')" $SqlConnection = New-Object System.

Thats right, many of us have been waiting for a standalone SP1 to upgrade our current SC 2012 implementations. However that could be a long wait since it will never happen. Microsoft has decided not to create a downloadable SP1, you will have to download the entire ISO to do an upgrade, if you can upgrade. DPM 2012 allows for an Upgrade VMM 2012 does not allow for an upgrade, its a complete re-install not sure about the others yet.

I am taking notes as i am doing my upgrade  to help any one who may have issues along the way. Make sure windows is updated completely Make sure you are doing your upgrade in the right order of SC products http://technet.microsoft.com/en-us/library/jj628203.aspx Before upgrading you will need Update Rollup 3 for DPM, you can get it here If you dont know if you have it, open you DPM console and click [ABOUT DPM] you will get a Version : 4.0.1920.0 (correct version) if any other version upgrade http://social.technet.microsoft.com/wiki/contents/articles/4058.list-of-build-numbers-for-system-center-data-protection-manager-dpm.aspx after the upgrade you will have to resync all your protection groups, If you did any modifications to the database you will re do it, IE: suspect tape removal, or Over due tape removal. Since im already upgraded i can move forward. Quick notes about my setup:  Single server : 2008 R2  SQL: 2008 R2 SP1  8GB memory  Dual Intel

Recently, Windows Update began offering the  Windows Management Framework 3.0  as an Optional update. This includes all forms of update distribution, such as Microsoft Update,  WSUS , System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0. Windows Management Framework 3.0 is being distributed as  KB2506146  and  KB2506143  (which one is offered depends on which server version you are running - Windows Server 2008 SP2 or Windows Server 2008 R2 SP1). What does that mean to you? Windows Management Framework 3.0 (specifically PowerShell 3.0)  is not yet supported  on any version of Exchange  except  Exchange Server 2013, which requires it. If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Exchange update rollups that will not install, or the Exchange Management Shell may not run properly. We have seen Excha