MDT 2012 - On Windows 2012 [PowerShell Initialization Error...]

So ... MDT 2012 on Windows 2012!!

When running MDT 2012 on Windows Server 2012 you get a Initialization Error, complaining about PowerShell being missing.

Try this...its a PowerShell execution policy issue.

http://sccmguy.com/2012/04/25/mdt-2012-with-server-2012-powershell-initialization-error/

Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

System Center 2012 ConfigMgr Advanced Infrastructure Session Notes

One of the best sessions I was able to attend in MMS 2013!

System Center 2012 ConfigMgr Advanced infrastructure session notes

Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

Powershell $Profile - UI Properties

Here are a couple commands that I found usefull for finding what and where I can tweek my UI.

Get-Host | Get-Member

 

(Get-Host).UI | Get-Member

 

(Get-Host).UI.RawUI | Get-Member

 

 

(Get-Host).UI.PrivateData | Get-Member

 

 





Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

Powershell $Profile - Color Changes

So I have finally gotten around to changing the format of my command windows in Powershell.

(Better late than never...)

So a couple of things,

1. You use "$host.UI.RawUI." for standard color changes but i noticed that the errors and warnings do not carry over the color changes and you get a block text inserts. So I found you also need to change the "$host.PrivateData." to handle those system responses.

2. Identifying the "Administrative" command shell. I like to visually see a difference when I am in Administrative mode, so below i use a simple IF statement to identify my shell state by triggering off the title. I then change color and my prompt.

3. I added a clear statement at the end of the profile to get a clean screen.

a section of my profile below...

#Host Config
If ($host.UI.RawUI.WindowTitle -match “Administrator”)
{
$host.UI.RawUI.BackgroundColor = “White”;
$host.UI.RawUI.ForegroundColor = “Black”;
$host.PrivateData.ErrorForegroundColor = “Red”;
$host.PrivateData.ErrorBackgroundColor = “White”;
$host.PrivateData.WarningForegroundColor = “Yellow”;
$host.PrivateData.WarningBackgroundColor = “White”;
$host.PrivateData.DebugForegroundColor = “Yellow”;
$host.PrivateData.DebugBackgroundColor = “White”;
$host.PrivateData.VerboseForegroundColor = “Yellow”;
$host.PrivateData.VerboseBackgroundColor = “White”;
$host.PrivateData.ProgressForegroundColor = “Yellow”;
$host.PrivateData.ProgressBackgroundColor = “White”;
Function Prompt{"PS[Administrator:]\>"}
}
Else
{
$host.UI.RawUI.BackgroundColor = "Black”;
$host.UI.RawUI.ForegroundColor = "DarkGreen”;
$host.PrivateData.ErrorForegroundColor = “Red”;
$host.PrivateData.ErrorBackgroundColor = “Black”;
$host.PrivateData.WarningForegroundColor = “Yellow”;
$host.PrivateData.WarningBackgroundColor = “Black”;
$host.PrivateData.DebugForegroundColor = “Yellow”;
$host.PrivateData.DebugBackgroundColor = “Black”;
$host.PrivateData.VerboseForegroundColor = “Yellow”;
$host.PrivateData.VerboseBackgroundColor = “Black”;
$host.PrivateData.ProgressForegroundColor = “Yellow”;
$host.PrivateData.ProgressBackgroundColor = “Black”;
$host.UI.RawUI.WindowTitle = "My Windows PowerSHELL"
}

#clear
Clear-Host

This is no where near all that I have or all that is possible, but i found this to be a neat way to colorize my shell experience.

Note: Tested in Powershell V3

Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

WDS - Changing Default Remote Install Folder

So after doing the initial install of WDS on Server 2012, realized I had set the remote install folder path incorrectly.

I wanted to see if it could be reset rather than re-installing WDS...

Never fear this thread on Technet had the solution, thanks to Tim Quan!

Open a Powershell command shell, type..

wdsutil /Uninitialize-Server

wdsutil /Initialize-Server /REMINST:"%new path%"

Your path is now reset.

Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

VMware White Box - Home Lab

So after reading several VMware home lab setup articles I decided to build my lab.

I started with ESXi 5.0 update1 but I had issues with it recognizing the mSATA disk.

So after downloading ESXi 5.1 all was good!

I am starting out with a single VMware server using the parts below, running ESXi 5.1.

Note: (Purchased March 2013)

1. Shuttle xPC SZ77R5 
2. Intel Core i7-3770 LGA1155
3. Crucial mSATA mPCI-E 32GB
4. Mushkin DDR3 PC12800 - 32GB RAM Kit
5. 2 x 1TB Seagate SATA disks
6. 1 x LightScribe SATA CD-Rom

Finished Box:

All hardware was recognized, even the on-board LAN card and I had ESXi up and running in 30 minutes.

This box is very quiet and with ESXi 5.1 it was very simple to build.

Note: The motherboard BIOS is the latest "SZ77R000.111"

Hope this helps.

All information is provided on an AS-IS basis, with no warranties and confers no rights.

How to Rename SCCM 2012 Site Name

I fat fingered my "site name" in SCCM 2012 and wanted to see if there was a way to correct my bad typing.. and I found this article by "Anoop".

Config Manager 2012 - How to edit site control sitectrl file

FYI, this process has always been performed in LAB environments and not in production, always contact Microsoft for advice on "Production" changes....!

Hope this helps!

All information is provided on an AS-IS basis, with no warranties and confers no rights.