Friday, September 13, 2013

WakeUp! a small GUI to wake Windows Machines from a PowerShell script

Because i need it so much i took the script i published before on link and enhanced it with a little GUI. here is a screenshot:

wakeup

It works like the script; the input is the MAC address from the line after MAC Address above and the script converts the MAC address to a unicast Wake on LAN packet. Next it will sent it through all connected Network adaptors connected.

On the Settings tab there are two lines: the DNS domain and the DHCP export file; used for retrieval of the cached MAC addresses.

It works like this: just type the machine name on the Computer Name line and hit Wake Machine the script will try to fetch the MAC address from the DHCP export. another way to use this app is to input the MAC address (with or without computer name) and hit Wake Machine this will also work.

wakeup2

Information about the DHCP Export can be found here (again) .

The two lines on the settings tab are reset to default every time the scripts starts. to change these lines to your own default, edit lines:  289 and 320 from the script.

wakeup3wakeup4

the script can be downloaded here: http://sdrv.ms/ZyH49Q

please beware, it is not signed, smart screen will warn you about that.

‘Good morning to you machines”

Wednesday, September 11, 2013

How to Setup SQL Server for Config Manager 2012 SP1 (SCCM)

Because i have had quite some trouble setting up a SQL Server for Config Manager 2012 on a separate server i decided i should write this down and share it to other people having similar problems:

So for Config Manager 2012 the requirements for a database are the following (excerpt from http://technet.microsoft.com/en-us/library/jj628198.aspx)

System Center 2012 SP1 component SQL Server 2008 R2 SP1 Standard, Datacenter SQL Server 2008 R2 SP2 Standard, Datacenter SQL Server 2012 Enterprise, Standard (64-bit) SQL Server 2012 SP1 Enterprise, Standard (64-bit)

App Controller Server

Data Protection Manager (DPM) Database Server

Operations Manager Data Warehouse

Operations Manager Operational Database

Operations Manager Reporting Server

Orchestrator Management Server

Service Manager Database or Data Warehouse Database

Virtual Machine Manager (VMM) Database Server

 

SQL server installation

To install an SQL server just follow the standard installation for a server and DO NOT SELECT EXPRESS version; SCCM Central site does not support EXPRESS versions of SQL server.

During installation of SQL the only thing to remember is: select a domain account for the SQL Server service:

sqlserver3

I am a typical IT admin so i am lazy when it comes to configuration in a test lab, so i used the domain administrator account for this test version; please do not do this in a production environment; be a good boy/girl and create a service account for this!

After the installation of SQL server has finished you have to configure the server for  three things:

  • Firewall
  • SQL configuration
  • Local administrators of the SQL server

The first one is quite simple: fire up the Firewall application and add a port rule for TCP 1433 and TCP 4022 to allow minimally the Domain profile.

sqlserver4

SQL installation itself does also add the SQLServer x64 to the firewall, this can stay because it does not do any harm.

Next the SQL configuration: this one did cost me most of my time because i did not notice the message:

The instance name that you use for the site database must be configured with a static TCP port. Dynamic ports are not supported

sqlserver1

This is really important: so i repeat : DO NOT USE DYNAMIC TCP PORTS ON SQL SERVER FOR THE SITE DATABASE OF SCCM 2012

The configuration of the sql service look like this:

sqlserver2sqlserver5sqlserver6

remember: the TCP Dynamic ports must be blank on all IP’s you use. also the TCP ports all must have 1433 when you use this (default) SQL server port for SQL transactions.

The last configuration is the addition of the SCCM server computer account to the local administrators group of the SQL server because i you don’t you receive an error like this in the prerequisites check of SCCM 2012 SP1

sqlserver7

to enable this do the following:

Open the local user and groups MMC on the SQL server and open the group administrators: add the COMPUTER account of the SQL server to this group, like this:

sqlserver8

after this, the prerequisites check should be fine and the SQL portion of the installation is complete.

See you next time!

Monday, September 09, 2013

Handy Computer scanner

When you do individual computer migrations it is desirable to get some computer- software- logged on user- and patch information on beforehand about the to-be-migrated computer.
For this i have bundled a few scripts i created and used before and wrapped them into one GUI to scan a machine and get the information presented in a GUI.
Here are some screenshots:
computerscannertab1


computerscannertab3
The scanner works real easy: just input the computer name and hit Get Computer Information. or just hit <Enter>

This version exports a csv to a path specified behind the Export to CSV checkbox. by default the checkbox is checked.
to change this behaviour goto line 1143 and edit the line to:
$cbExport.Checked = $False

To change the location to which the CSV file is written, edit the line: 1137
$tbCSVExport.Text = "D:\Software\_ScannerOutput\%Computername%.csv"

For the scanner to work the target computer must be WMI- and remote registry enabled. Links: http://kb.gfi.com/articles/Skynet_Article/how-to-enable-remote-registry-through-group-policy
http://kb.gfi.com/articles/Skynet_Article/how-to-enable-remote-registry-through-group-policy

The script can be downloaded here: http://sdrv.ms/166HegJ

Friday, September 06, 2013

PowerShell Array’s inside-out

 
Learning PowerShell is one thing, but learning arrays in PowerShell is another. Since i started using PowerShell as my primary programming- and scripting language i have stumbled on this array stone many times.

Now it is time to really get to the bottom of this.

What’s an array

Arrays are, bluntly put, programming variables with more functionality and more space in this view an array can be used as a variable in your PowerShell code. as a matter of fact most beginners do experience arrays as a variable certainly in the beginning. that is because arrays do tend to work exactly like  a variable when it only has one item and one value. look at this example:
[string]$Variable="one value"
[array]$array= @("one value")

$Variable
"---------"
$array

This code will display exactly the same return codes when run.

one value
---------
one value

now look at this:
[string]$Variable="one value","one value","one value"
[array]$array= @("one value","one value","one value")

$Variable
"---------"
$array
this will output:
one value one value one value
---------
one value
one value
one value

Here you will see the first differences between a variable and an array. The variable will handle the value as one string while the array will display 3 strings in an row.

PowerShell will use default values for options you do not present. In this case PowerShell will present the entire $variable as a string because you defined the variable as a string so the output will also be a string. with the array we defined a one dimensional array. because of that the output of the array to the default output (screen) will the the presentation of 3 objects, each presented on its own row. you can see the differences even more when you request PowerShell to return a specific item of a variable or array:
[string]$Variable="one value","one value","one value"
[array]$array= @("one value","one value","one value")


PS C:\Windows\system32> $Variable[0]
o

PS C:\Windows\system32> $array[0]
one value

As can be seen from this example the first item of the variable is the first character of the string while the first item of the array is the first object.

Array dimensions


Arrays come in two flavours: one-dimensional and multi-dimensional. the one-dimensional is shown above so lets look at multi-dimensional arrays:

a multi-dimensional array is defined like this:
$MultiArray = @(("one","two"),
             ("three","four","six"))



To retrieve the entire array a simple $MultiArray will suffice but retrieving a specific item from an array like this is done a bit different.

Say you would like to retrieve the second item from the second row, how do you do that?
$MultiArray[1][1]
four

So the trick is to define the item you want to retrieve and define it in square brackets [ ] one for the row to select (the number in the first bracket) and one number for the column (the number in the second bracket) the count of rows and columns is from 0, so row 1 is [0]

Handy tricks in multi-dimensional arrays


There are some nice ‘tricks’ with multi-dimensional arras:


  • retrieve the last item of a row:
$MultiArray = @(("one","two"),
             ("three","four","six"))

$MultiArray[1][-1]
six

So you give a –1 for the last item to be retrieved. so how to retrieve the second last item of row 1?
$MultiArray = @(("one","two"),
             ("three","four","six"))

$MultiArray[0][-1-1]
one


  • retrieve items 2 to 4 from row 2 from an array
$MultiArray = @(("one","two"),
             ("three","four","six","seven","eight","nine"))

$MultiArray[1][2..4]
six
seven
eight

To really get this down have some fun with it like building a loop to get things done:
$MultiArray = @(("one","two"),
             ("three","four","six","seven","eight","nine"),
             ("ten","eleven")
)

$noRows=$MultiArray.Count

for($i=0;$i - $noRows;$i++){$rownow=$null
    [string]$rownow += $MultiArray[$i]
    [array]$gridarray += $rownow}
$gridarray

one two
three four six seven eight nine
ten eleven

That is about it, you should really have a go and do some things with arrays to get to know them well.

See you next time.

Tags van Technorati: ,,

Tuesday, August 27, 2013

MDX sources

Dear reader, since my last posts i informed you about MDX and its workings.
in this post i proudly present the MDX sources.
In the link at the bottom of this post an .MSI can be found that will install MDX on a system. the .MSI will install the MDX script, the readme and the manual
The installation has been tested on Windows Server 2003 and Server 2008 R2. here is the readme:

Welcome to MDX
This application is written in PowerShell, to successfully start it you need to have powershell (version 2.0 and up) installed on the machine you're installing to
At first launch your settings will not reflect the settings of your deployment environment. please take your time to set the settings of MDX. refer to the manual for detailed information and usage of MDX and its settings.
On PowerShell 2.0 some parts of MDX will not work; for instance the MDT Settings Extra Apps will not show when using PowerShell 2.0.
To get things started PowerShell needs to have its execution policy set to remotesigned or lower because this script is NOT signed. please refer to http://technet.microsoft.com/en-us/library/ee176961.aspx for more information about PowerShell signing
MDX will be installed to C:\Program Files\MDX by default, feel free to change that is you want to but always check its working after this.
MDX works with a few tools locally to get fully started. in the installation MSI some of these files are incorporated, they will be installed to its default locations. the extra files are:
    - MDXIcoon1.jpg
    - Manual MDX.docx
    - Readme.txt
PsExec from the PStools must be installed on the system, preferably on a path location from your SET.
link: http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx

The MDTDB from Michael Niehaus also is a MUST, the installation points to the C:\Windows\System32\WindowsPowerShell\v1.0\Modules\MDTDB directory so you can best copy the module to that path.here is the link to Michaels blog:
http://blogs.technet.com/b/mniehaus/archive/2009/05/15/manipulating-the-microsoft-deployment-toolkit-database-using-powershell.aspx
MDX’s registry entries are set in the installation of the MSI, they can be changed in the settings tab of MDX.
MDX will connect to machines through WMI, for this mechanism to work in Windows Firewall enabled machines the following rule must be enabled in the network location profile
   
    - Windows Management Instrumentation (DCOM-In)
    - Windows Management Instrumentation (WMI-In)

Also MDX will try to ping machines; for this to work the following rule must be enabled on firewalled machines:
    - File and Printer Sharing (Echo Request - ICMPv4-In) (when using IPv4 traffic
    - File and Printer Sharing (Echo Request - ICMPv6-In) (when using IPv6 traffic

Last but not least: for the remote starting via PSExec the - Remote Desktop - User-In must be opened.
PsExec itself will require a litetouch user account that has to me member of the AD group "Remote Desktop Users"
For Wake on LAN to work the used Network segments must not prohibit WOL broadcasts. please do keep in mind WOL broadcasts cannot traverse Routers, so one MDT server can only service as much network segments it is connected to.
PXE control will only work under specific conditions. please refer to link: http://www.ithastobecool.com/2009/08/17/zerotouch-for-mdt-2010-without-sccm/
to get a clear understanding of this subject.
Happy deploy-ing
Bas Huygen
negyuh@xs4all.nl

I hereby would like to thank the following technical documents and its writers:
Furthermore i would like to thank the following Colleagues for support and testing:
  • Barry Mes
  • Ylber Tahiri

Download the MDX installers here:
  - x86: https://skydrive.live.com/redir?resid=12B72EEE2C1F9871!2587
   -x64: https://skydrive.live.com/redir?resid=12B72EEE2C1F9871!2588
Please note! this installer nor the PowerShell script has been signed; Smart screen filters will warn you about that fact! 
I am still working on a valid certificate…
The MDX manual can also be downloaded separately: https://skydrive.live.com/redir?resid=12B72EEE2C1F9871!2589
I fully understand that this is the first version, feel free to download this installer and use it, when you will find a bug or think MDX should definitely use a new feature; feel free to contact me at:
mdx@xs4all.nl
Happy deploying and till next time.



Saturday, August 24, 2013

MDX technical design

Hi folks, as promised i present the next part of my MDX posts. This time i will elaborate on the technical part of MDX as well as give you, the reader, a view of how  OS deployments are done; the MDX way.

MDX design; technical facts

MDX is build in PowerShell, the GUI is designed in SAPIEN’s Primal Forms Community Edition and the application is programmed in Microsoft’s own PowerShell ISA. the script counts around 3000 lines of code of which roughly 2000 lines are accounted for by the GUI. the script is divided in 15 Functions and 6 sections.

The general idea of the applications is: unification and simplification of MDT and accompanying tools to an end-to-end deployment solution.

mdx opbouw

Architecture

MDX is designed around the functionality of a few components:

Here is the graphical representation of the design

Architecture MDX

MDX has a few sections that do the work. each section does a part of the total solution; for example there is a section in MDX that accepts input from the GUI checks its validity and, if verified, adds or modifies a corresponding computer item in MDT- in its database. another section does communicate with PzExec.exe and adds the needed variables to the tools to get a deployment started.

How does MDT accomplish end-to-end automated deployment?

The ‘secret’ of MDX is the way all under laying components are ‘orchestrated’ to make a ‘deployment symphony’ …. the way MDX does this is as follows:

  • MDX controls the MDT database (which is crucial for end-to-end automated deployments) via PowerShell
  • MDX takes variables from the UI and combines it with preconfigured components in MDT and other used tools
  • MDX manipulates a computer object from the MDT database in such a way that it is deployment ready
  • MDX adds ‘non standard’ items or features to the preconfigured building blocks like: for example: add a few applications to the deployment of a certain computer and adds a user account as local administrator to the same deployment as well
  • MDX controls the WDS PXE server and thus controls who may- and may not boot to PXE and do a deployment via the network
  • MDX can directly fire a preconfigured computer to do a deployment.

What is to be expected from doing deployments with MDX

Apart from the fact that MDX takes away the direct interaction with MDT, MDX will give the User direct control over all building blocks of the deployment chain from a single GUI. the user can start off with a computer name, check the settings and modify them and fire of the deployment to the machine.

One important thing to realize is: MDX will help the user to select ALL settings and set them without the possibility of human error (like typing). MDX eases these tasks by presenting a simple but effective UI that will help de user select those things needed MUCH faster AND easier than when he- or she would do manually in MDT itself. as a bonus it eases the management of tools like WDS or the start of MDT deployment in the traditional way.

The next post will present a real world example of deployment with MDX. till next time.

Thursday, August 22, 2013

Introducing MDX

The last weeks is have not published anything since i was working on an IT solution i am introducing here on this page.
The next posts i will elaborate and present the code of my application, this is part 1: the introduction:
MDX stands for MDT Deployment eXerience. and it is a solution targeted at Microsoft OS deployment with MDT. So you can ask me; what does it do and, even more important, what does it add to MDT since that is quite a mature OSD solution in itself. my answer will be: MDT indeed is a very great OSD solution but it has its drawbacks. let me mention a few of them:
  • The interface of MDT is quite cumbersome in respect to manipulating individual computer deployments.
  • MDT does not have any functionality to automatically start a deployment on a client
  • MDT needs ‘start-up media’ to get a deployment running like a CD or USB stick, although MDT can deliver a distribution via the network, it does not have any mechanism to control PXE servers
Because of these (and many more) drawbacks i decided to develop my own ‘shell’ around MDT and address these items.

So what does MDX do?

since i always think images speak louder then words I'll show you the interface.

As you can see the Application has its own GUI, in it there are a few input sections-, output sections and some buttons to get the whole thing running. MDX was built in PowerShell, the code for the GUI was generated by SAPIEN’s Primal Forms Community edition
MDX can do the following:
  • On input of a computer name it will try to fetch a MAC address of the particular machine, if found it will use it to add- or find this machine in MDT and attach OSD properties to it to get it deployed
  • MDX will show Computer information when the machine is online; this can be quite handy when you are to be migrating existing computers from say Windows XP to Windows 7 or 8
  • MDX has a direct link with Microsoft's WDS servers, with this link it can control PXE boots of WDS clients
  • MDX can wake a machine with Wake On LAN with one push on a button
  • MDX can start a deployment remotely with the use of PS Exec.exe (a fine piece of toolkit developed by Mark Russinovich), with this it can completely automate MDT deployments to clients.
  • MDX can add extra applications to a individual OS deployment- as well ass add an account to the local administrators group.
Al together i think it will add some nice features to MDT or as a colleague remarked “this is real automation with budget (freeware) tools!”
Next post i will elaborate on the technical workings of MDX, if all goes well i will present a download link to the source code.
till next time.