Search results for 'app:weblogs' matching tag 'scripts'

Building A Hyper-V Test Lab on Windows 8 – Part 5 Configuring DC1

Anonymous — Mon, 04 Feb 2013 06:00:00 GMT

Introduction

This the fifth part in a multi-part set of articles on building a test lab with Hyper-V and PowerShell. See the following prior articles in this series.

Configuring the First DC

In the last article, I showed you how to create a domain controller in a new forest. The DC provides the AD environment for the rest of the VMs in my test lab so has to become the DC before any other VMs are created. In this article I present a second configuration script for the domain controller, snappily named Configure-DC1-2.ps1. This second script just finishes off the configuration and setup of the DC, after it' was promoted to being a DC.

Once the DC1 has been created and promoted to being a domain controller, you configure it to add the features and configuration I need in labs and for writing projects.

From a work flow perspective, once the DC has been created, creating and configuring other new VMs can be done in parallel with configuring DC1. If you are creating VMs that rely on DHCP, you would need to complete the configuration before those VMs are created. And, of course any new VMs created are domain joined use a different Unattend.XML file in the creation of the VM.

In my lab’s case, configuration the first domain controller, DC1, is pretty simple:

Set the VM to automatically logon as the domain admin – in lab environments, life really is too short to have to type credentials any more than is absolutely needed. So I set the registry settings to enable auto admin logon
Install Key Windows features - I include some simple features, including IIS (which is needed to enable the DC to be a CA).
Install and configure basic DHCP - Most of my lab machines have fixed IP addresses, but having a small DHCP block seems a good thing! I configure this with some basic options.
Create some basic users/groups/OUs in the AD – I just create a couple of demo users, a couple of AD OUs and add the new accounts to some groups. I have a further script Configure-ReskitAD.ps1, as part of this series, that adds a richer AD environment.

Once that has been done, I do two more things in the script:

Force a reboot of the VM
Take a snapshot of the DC. This is useful if I want to do some AD configuration but then back out of that.

Using Remoting to Configure DC1

In the first two scripts that create and start up the VM, the scripts contain a function definition that is then run against the local system, i.e. the host you are using to run Hyper-V. In my case, this was done on Windows 8 on my laptop and one of my Server 2012 boxes. They both run Hyper-V well so testing is easy both at home and on the road. As I noted previously, the remainder of the scripts I use that to setup and configure the domain and servers use remoting. The following pattern if these scripts is as follows:

Create a script block, $CONF or similar, containing PowerShell code to perform some configuration on a server. The PowerShell code is intended to run in the target VM.
Use Invoke-Command, and the appropriate credentials, to run that script block on a remote server (i.e. one of the Hyper-V VMs you are building/configuring.

This process is flexible and allows me to do things before invoking the script block. For example, to install SQL, Exchange or Lync, I need to have the product CD inserted in the D: drive. For Exchange, I have to load some pre-requisites onto the server, for example bits of IIS, etc. that are not needed for other labs. SO in that case, the configuration script file can create a couple of script blocks to divide up the work. In the longer term I consolidate the multiple script blocks, but that’s work to be done!

Snapshotting VMs

These scripts were designed to support me in writing and developing courseware. Since the development work can be error-prone plus with a need to test, test, and re-test lab instructions, I need to take snapshots before and after key configuration events. So what this script does, at the very end, is to take a VM snapshot and label it as being created by this script. You can, of course, comment out this if you don’t need to have a snapshot!

Using the Scripts

When I am building out a new set of VMs, I open ALL these scripts in the ISE on the Hyper-V host. Whilst I am at home, that means running these via a terminal services window against one of my Hyper-V servers or my laptop. Once I have all the scripts open, I just work through them, tweaking the unattend.xml, building the base disk, building then promoting DC1, finishing off DC1 configuration, configuring a CA, configuring the IIS servers, etc.

Getting the Scripts

I have published the full set of deployment scripts to my web site, at http://www.reskit.net/powershell/vmbuild.zip. Note that some of the scripts in this zip file are very much works in progress that are changing, and hopefully improving, as I publish these articles. I reserve the right to change any of all of them from time to time. I will try to blog any important changes.

I am also publishing the individual scripts over on my PowerShell Scripts Blog:

Recent Script Changes

Since starting this series, I’ve been tidying up the scripts. In some cases, I’ve moved parameters into hash tables to increase readability. The changes to the scripts are now added to the script itself. One key change is that I set Auto-Admin logon for all servers, and force a reboot of the server after configuring it. I’ve also added some judicious Hyper-V check pointing into some of the scripts to simplify both further testing and to suit my courses.

Future Scripts

The next couple of scripts, which I hope to get documented this week, including building and configuring general purpose servers and creating a Certificate Authority. I also have some utility scripts that I have added and will also be documenting.

Comments

Any comments? I’d love to hear from you – either as comments to this blog post, or via email.

Technorati Tags: Deployment scripts,PowerShell,Hyper-V

Configure-DC1-2.ps1

Anonymous — Mon, 04 Feb 2013 06:00:00 GMT

# Configure-DC1-2
# Configures DC1 after dcpromo is completed
# Version 1.0.0 - 14 Jan 2013
# Version 1.1.0 - 24 Jan 2013
# Added code to count how long it all took.
# Added a checkpoint at the end of DC1 configuration
# Version 1.1.1 - 25 Jan 2013
# Added auto admin logon - need to reboot VM for it to work.
# Configuration block
$conf = {
$StartTime = Get-Date
Write-Host "Starting at: $StartTime"
# Set Credentials
$Username = "Reskit\Administrator"
$PasswordSS = ConvertTo-SecureString -string 'Pa$$w0rd' -AsPlainText -Force
$Credrk = New-Object -Typename System.Management.Automation.PSCredential -Argumentlist $Username,$PasswordSS
# Define registry path for autologon, then set admin logon
$RegPath = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon'
$User = 'Administrator'
$Password = 'Pa$$w0rd'
$Dom = 'Reskit'
Set-ItemProperty -Path $RegPath -Name AutoAdminLogon -Value 1 -EA 0
Set-ItemProperty -Path $RegPath -Name DefaultUserName -Value $User -EA 0
Set-ItemProperty -Path $RegPath -Name DefaultPassword -Value $Password -EA 0
Set-ItemProperty -Path $RegPath -Name DefaultDomainName -Value $Dom -EA 0
# Install key Windows features for labs
Install-WindowsFeature PowerShell-ISE, Rsat-AD-PowerShell, Hyper-V-PowerShell, AD-Domain-Services, Web-Server -IncludeManagementTools
# Install and configure DHCP
Install-WindowsFeature DHCP -IncludeManagementTools
Add-DhcpServerV4Scope -Name "ReskitNet0" -StartRange 10.0.0.100 -EndRange 10.0.0.119 -SubnetMask 255.255.255.0
Set-DhcpServerV4OptionValue -DnsDomain Reskit.Org -DnsServer 10.0.0.10
Add-DhcpServerInDC -DnsName Dc1.reskit.org
# Add users to the AD and then add them to some groups
$pw = 'Pa$$w0rd'
$psss = ConvertTo-SecureString -String $pw -AsPlainText -Force
# Hash table for common new user paraemters
$NewUserHT = @{AccountPassword = $PasswordSS;
Enabled = $true;
PasswordNeverExpires = $true;
ChangePasswordAtLogon = $false
}
New-ADUser @NewUserHT -SamAccountName tfl -UserPrincipalName 'tfl@reskit.org' -name "Thomas Lee"
New-ADUser @NewUserHT -SamAccountName bb -UserPrincipalName 'bb@reskit.org' -name "Billy Bob Joe Bob"
New-ADUser @NewUserHT -SamAccountName sb -UserPrincipalName 'sb@reskit.org' -name "Sue Bob Joe Bob"
New-ADOrganizationalUnit -Name 'IT Department'
Move-ADUser
Add-ADPrincipalGroupMembership -Identity "CN=User1,CN=Users,DC=reskit,DC=org" -MemberOf "CN=Enterprise Admins,CN=Users,DC=reskit,DC=org" ,"CN=Domain Admins,CN=Users,DC=reskit,DC=org"
Add-ADPrincipalGroupMembership -Identity "CN=User2,CN=Users,DC=reskit,DC=org" -MemberOf "CN=Enterprise Admins,CN=Users,DC=reskit,DC=org" ,"CN=Domain Admins,CN=Users,DC=reskit,DC=org"
Add-ADPrincipalGroupMembership -Identity "CN=User3,CN=Users,DC=reskit,DC=org" -MemberOf "CN=Enterprise Admins,CN=Users,DC=reskit,DC=org" ,"CN=Domain Admins,CN=Users,DC=reskit,DC=org"
# Say nice things and finish
$FinishTime = Get-Date
Write-Host "Finished at: $finishtime"
Write-Host "DC1 Configuration took $(($FinishTime - $StartTime).TotalSeconds.ToString('n2')) seconds"
# Reboot
Restart-Computer -ComputerName DC1 -Force
}
# Start of script proper
# Set Credentials
$Username = "Reskit\administrator"
$PasswordSS = ConvertTo-SecureString -string 'Pa$$w0rd' -AsPlainText -Force
$Credrk = New-Object -Typename System.Management.Automation.PSCredential -Argumentlist $Username,$PasswordSS
# Following code used to test the credentials. Remove the comments on next two lines the first time you
# run this script
Invoke-Command -ComputerName DC1 -ScriptBlock {hostname} -Credential $Credrk -verbose
Pause
Invoke-Command -ComputerName DC1 -Scriptblock $conf -Credential $Credrk -verbose
# Finally, run a post-DCPromo snapshot
Checkpoint-VM -VM $(Get-VM DC1) -SnapshotName "DC1 - post configuration by ConfigureDC1-2.ps1"

Technorati Tags: PowerShell,V3,VM,Scripts

Building a Hyper-V Test Lab on Windows 8 – Part 1

Anonymous — Sun, 13 Jan 2013 06:00:00 GMT

This is the first part of a multi-part blog article on a set of scripts to create VMs using Microsoft’s Hyper-V on both Windows 8 and Server 2012.

Background

For many years, I’ve used virtual machines heavily. The articles, courses and books I write rely on VMs for their content. I’ve lost count of the number of domains I’ve built, re-built, broken, fixed over the years.

The only downside is that I was regularly building and re-building the systems by doing creating a new VM and installing the OS from scratch. This was slow and tedious as well as somewhat error prone.

What I needed was a good, reliable system of creating sets of VMs and configuring them. The base set of services I want to be able to install and use was not that long: the OS (with AD, ADCS, DHCP, DNS, File Services), SQL, and Exchange.

Now that I have these scripts working, or nearly so, I am amazed at how much easier it is to create a set of VMs for particular purpose (e.g. write an article, create a class, build a demo for a talk). I am also finding others that have similar needs. I hope others find these scripts useful!

Building VMs Using Scripts

In the autumn of 2012, I, along with super-star MVP colleague Niklas Goude, started running PowerShell Geek Weeks in Stockholm. A lot of fun – 5 days of going as deep as we can with PowerShell. A key part of the Geek Week adventure is for the delegates to build their own environment AND to be able to take away the tools to re-create this environment at home.

I spent quite some time building some basic scripts – and encountered a lot of dead ends along the way. The first time out was a limited success – limited in that some pieces did not fit together well but a success in that it taught a lot of cool PowerShell features and showed us where we needed to do more. It also helped me to refine the real objectives the tools had to meet. Thanks goes to Mikael Nystrom for helping me with a good starting Unattend.XML!

Objectives of the VM Build module

My main objectives of these build tools were:

1. To enable someone with fairly limited PowerShell skills (or greater!) to use the the scripts simply and flexibly in the classroom and later.

2. To enable building out of a small farm of up to say half a dozen servers with minimal effort.

3. To enable extensibility, in that one could add more scripts to refine the configuration (e.g. adding a script to implement a failover DHCP).

4. To encode things like domain/forest names, user ids, passwords and IP address information to a given standard but make it not too difficult to change that.

5. To avoid the user having to use too much of the new automated setup approach.

6. To keep the use of disk space to a minimum.

The Architecture

The basic architecture of what I am trying to build is shown here:

The idea is simple – a single reference, parent, disk with a number of separate VMs based on differencing disks. This approach hits objective 6, and enables a simple solution to objective 4.

The Scripts

The key scripts here are as follows:

Create-ReferenceVHDX – this script creates a parent VHDX based on an image from the Install.WIM from a Server (or client) installation DVD.
Create-VM – this script creates a differencing VHDX, based on the reference VHDX, and creates an updated Unattend.xml file, stores this on the differencing drive. The script then starts the VM which then installs Windows onto the differencing disk. You run this script to create the VMs and VHDXs for DC1, Exch1, SQL1, SRV1, SRV2.
Configure-DC1-1 – this script turns the first VM, DC1, into a domain controller in a new forest.
Configure-DC1-2 – this script configures DC1, post installation as a DC. This includes adding and configuring DHCP and creating some users in AD.
Configure –DC1-CA – this script convers DC1 into an Enterprise Root CA, and creates a web responder, complete with SSL support for the /Certsrv application.
Configure-Exch1 – this script configures the Exch1 VM, including installing Exchange 2008 on the Exch1 VM.
Configure SQL1-1 – this script configures the SQL server VM, including installing SQL server itself.
Configure-SRV1-1 - Configure-SRV2-1, these scripts create a pair of application servers, including adding all of the RSAT tools and IIS.
Utility Scripts – these include Set-DVDDriveOnAll (sets a particular DVD/ISO to be in the DVD drive of all VMs), Set-LanguageOnAll – sets the administrator logon have a particular kb layout for all vms, Set-NetFrameworkCoreOnAll (adds the base .NET onto all systems – which is needed for PowerShell V2).

What’s Next?

There are several next steps:

Get all these scripts uploaded to my DropBox – I need to do a bit more tidying up then these will be ready for viewing.
I’ll publish each script both to the PowerShell scripts blog (http://pshscripts.blogspot.co.uk) as well as publishing details of each scripts here. IN publishing the details here, I’ll explain what each script is doing and why I did it that way. As ever, comments are welcome – and may cause further updates to the script set!
I’ll update this page with pointers and anything updated as I complete this set of posts.
Package these scripts up as a downloadable module. Right now, these are just a bunch of scripts and some XML – making a proper module out of it is high on my agenda.
Do a better job of centralising the variables across the scripts – things like user name, password, domain name, etc. I had in mind an XML file with all the key stuff in just one place!
Take feedback and refine. Comments on these scripts are most welcome.

Summary

With the release of Server 2012 and Windows 8, building a set of Hyper-V VMs is now easier than ever – and these VMs can easily be moved from server to client and back as needs dictate. The set of scripts I’ve created have helped me create lab environments quickly and easily and may help you too.

Comments most welcome!

Technorati Tags: PowerShell,Implementation,Deployment,Scripts

Show-Formatting1.ps1

Anonymous — Tue, 07 Aug 2012 05:00:00 GMT

<#
.SYNOPSIS
MSDN Sample Recoded in PowerShell demonstrating formatting
.DESCRIPTION
This sample recodes an MSDN Sample into PowerShell that
shows some of the options of formatting using ToString() and
various .NET formatting strings
.NOTES
File Name : Show-Formatting1.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://www.pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/0c899ak8.aspx
.EXAMPLE
Psh> .\Show-Formatting1.ps1\
00123
1.20
01.20
01,20
0.6
1,234,567,890
1.234.567.890
1,234,567,890.1
1,234.57
#>
## Start script
[double] $value = 123;
$value.ToString("00000")
# Displays 00123
$value = 1.2;
$value.ToString("0.00", [System.Globalization.CultureInfo]::InvariantCulture)
# Displays 1.20
$value.ToString("00.00",[System.Globalization.CultureInfo]::InvariantCulture)
# Displays 01.20
$value.ToString("00.00",
[System.Globalization.CultureInfo]::CreateSpecificCulture("da-DK"))
# Displays 01,20
$value = .56
$value.ToString("0.0", [System.Globalization.CultureInfo]::InvariantCulture)
# Displays 0.6
$value = 1234567890
$value.ToString("0,0", [System.Globalization.CultureInfo]::InvariantCulture)
# Displays 1,234,567,890
$value.ToString("0,0",
[System.Globalization.CultureInfo]::CreateSpecificCulture("el-GR"))
# Displays 1.234.567.890
$value = 1234567890.123456;
$value.ToString("0,0.0", [System.Globalization.CultureInfo]::InvariantCulture)
# Displays 1,234,567,890.1
$value = 1234.567890;
$value.ToString("0,0.00", [System.Globalization.CultureInfo]::InvariantCulture)
# Displays 1,234.57

Technorati Tags: PowerShell,Scripts,System.Globalization,formatting with PowerShell

Show-FileInformation.ps1

Anonymous — Sun, 20 Nov 2011 06:00:00 GMT

<#
.SYNOPSIS
This script displays information returned from the
file version object.
.DESCRIPTION
This script gets, then displays, all the information returned
from the System.Diagnostics.Fileinfo of Notepad.exe
.NOTES
File Name : Show-FileInformation.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://http://pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/system.diagnostics.fileversioninfo_properties.aspx
.EXAMPLE
Psh> .\Show-FileInformation.ps1
File Major Part for C:\Windows\system32\Notepad.exe is: 6
#>
# Set filename
$File = [System.Environment]::SystemDirectory + "\Notepad.exe"
#Get Version information for this file
$myFileVersionInfo = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($File)
# Display all the file information:
"FileInfo information for {0}" -f $file
"Comments : {0}" -f $myFileVersionInfo.Comments
"Company Name : {0}" -f $myFileVersionInfo.CompanyName
"FileBuldPart : {0}" -f $myFileVersionInfo.FileBuildPart
"FileDescription : {0}" -f $myFileVersionInfo.FileDescription
"FileMajorPart : {0}" -f $myFileVersionInfo.FileMajorPart
"FileMinorPart : {0}" -f $myFileVersionInfo.FileMinorPart
"FilePrivatePart : {0}" -f $myFileVersionInfo.FilePrivatePart
"FileName : {0}" -f $myFileVersionInfo.FileName
"FileVersion : {0}" -f $myFileVersionInfo.FileVersion
"InternalName : {0}" -f $myFileVersionInfo.InternalName
"IsDebug : {0}" -f $myFileVersionInfo.IsDebug
"IsPatched : {0}" -f $myFileVersionInfo.IsPatched
"IsPreRelease : {0}" -f $myFileVersionInfo.IsPreRelease
"IsPrivateBuild : {0}" -f $myFileVersionInfo.IsPrivateBuild
"IsSpecialBuild : {0}" -f $myFileVersionInfo.IsSpecialBuild
"Language : {0}" -f $myFileVersionInfo.Language
"LegalCopyright : {0}" -f $myFileVersionInfo.LegalCopyright
"LegalTrademarks : {0}" -f $myFileVersionInfo.LegalTrademarks
"OriginalFilename : {0}" -f $myFileVersionInfo.OriginalFilename
"PrivateBuild : {0}" -f $myFileVersionInfo.PrivateBuild
"ProductBuildPart : {0}" -f $myFileVersionInfo.ProductBuildPart
"ProductMajordPart : {0}" -f $myFileVersionInfo.ProductMajorPart
"ProductMinorPart : {0}" -f $myFileVersionInfo.ProductMinorPart
"ProductName : {0}" -f $myFileVersionInfo.ProductName
"ProductPrivatePart : {0}" -f $myFileVersionInfo.ProductMinorPart
"ProductVersion : {0}" -f $myFileVersionInfo.ProductVersion
"SpecialBuild : {0}" -f $myFileVersionInfo.SpecialBuild

Technorati Tags: PowerShell,scripts,System.Diagnostics,FileInfo

Show-FileVersionComments.ps1

Anonymous — Thu, 10 Nov 2011 06:00:00 GMT

<#
.SYNOPSIS
This script shows the company name of a file version object
.DESCRIPTION
This script is a re-implementation of an MSDN Sample script
that uses System.Diagnostics.FileVersionInfo to get
the company name (if it exists).
.NOTES
File Name : Show-FileVersionComments.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://www.pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/system.diagnostics.fileversioninfo.comments.aspx
.EXAMPLE
Psh> .\Show-FileVersionComments.ps1
Company name: Microsoft Corporation
#>
# Set filename
$File = [System.Environment]::SystemDirectory + "\Notepad.exe"
#Get Version information for this file
$myFileVersionInfo = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($File)
# Print the Comments field
"Commments : " + $myFileVersionInfo.CompanyName

Technorati Tags: PowerShell,Scripts,PowerShell script,System.Diagnostics.FileVersionInfo,GetVersionInfo

Show-FileVersionCompanyName

Anonymous — Thu, 10 Nov 2011 06:00:00 GMT

<#
.SYNOPSIS
This script shows the company name of a file version object
.DESCRIPTION
This script is a re-implementation of an MSDN Sample script
that uses System.Diagnostics.FileVersionInfo to get
the company name (if it exists).
.NOTES
File Name : Show-FileVersionCompanyName.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://www.pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/system.diagnostics.fileversioninfo.companyname.aspx
.EXAMPLE
Psh> .\Show-FileVersionCompanyName.ps1
Company name: Microsoft Corporation
#>
# Set filename
$File = [System.Environment]::SystemDirectory + "\Notepad.exe"
#Get Version information for this file
$myFileVersionInfo = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($File)
# Print the Company name
"Company name: " + $myFileVersionInfo.CompanyName

Technorati Tags: PowerShell,System.Diagnostics.FileVersionInfo,GetVersionInfo,scripts

Open-WordDocument.ps1

Anonymous — Wed, 09 Nov 2011 06:00:00 GMT

<#
.SYNOPSIS
This script opens a word document using PowerShell
.DESCRIPTION
This script re-implments a simple MSDN script to open
a word document using VBA. IT Pros using PowerShell
might also make use of to create rich documents as
output from a script.
.NOTES
File Name : Open-WordDocument.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://www.pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/bb148369%28office.12%29.aspx
.EXAMPLE
Running this sample opens the file c:\foo\doc1.docx in Word. The
COM object referring to the document is returned for later use.
#>
# Create Word Object
$wrd = new-object -com word.application
# Make Word Visible
$wrd.visible = $true
# Open a document
$doc = $wrd.documents.open("C:\foo\doc1.docx")

Technorati Tags: PowerShell,code,scripts,word.application,word,winword,script,PowerShell script

Show-UnicodeCharacters.ps1

Anonymous — Tue, 08 Nov 2011 06:00:00 GMT

<#
.SYNOPSIS
This script, a re-implementation of an MSDN sample, shows the
Unicode details of a unicode character, using PowerShell.
.DESCRIPTION
This script re-implements a simple MSDN script that takes a Unicode Character
and uses CharUnicodeInfo class to get details of that character, which are then
displayed.
.NOTES
File Name : Show-UnicodeCharacters.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://pshscripts.blogspot.com/2011/11/show-unicodecharactersps1.html
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/system.globalization.charunicodeinfo.aspx
.EXAMPLE
Psh > .\show-unicodecharacters.ps1
c Num Dig Dec UnicodeCategory
U+0061 LATIN SMALL LETTER A a -1 -1 -1 LowercaseLetter
U+0393 GREEK CAPITAL LETTER GAMMA Γ -1 -1 -1 UppercaseLetter
U+0039 DIGIT NINE 9 9 9 9 DecimalDigitNumber
U+00B2 SUPERSCRIPT TWO ² 2 2 -1 OtherNumber
U+00BC VULGAR FRACTION ONE QUARTER ¼ 0.25 -1 -1 OtherNumber
U+0BEF TAMIL DIGIT NINE ௯ 9 9 9 DecimalDigitNumber
U+0BF0 TAMIL NUMBER TEN ௰ 10 -1 -1 OtherNumber
U+0F33 TIBETAN DIGIT HALF ZERO ༳ -0.5 -1 -1 OtherNumber
U+2788 CIRCLED SANS-SERIF DIGIT NINE ➈ 9 9 -1 OtherNumber
#>
# Helper Function
Function PrintProperties {
param ($char)
$fmtstring = " {0,-5} {1,-8} {2,-9} {3,-9} {4,-9}"
$a = $char
$b = [System.Globalization.CharUnicodeInfo]::GetNumericValue( $char )
$c = [System.Globalization.CharUnicodeInfo]::GetDigitValue( $char )
$d = [System.Globalization.CharUnicodeInfo]::GetDecimalDigitValue( $char )
$e = [System.Globalization.CharUnicodeInfo]::GetUnicodeCategory( $char )
$fmtstring -f $a, $b, $c, $d, $e
}
" c Num Dig Dec UnicodeCategory"
"U+0061 LATIN SMALL LETTER A " + (PrintProperties "a")
"U+0393 GREEK CAPITAL LETTER GAMMA " + (PrintProperties ([Char] 0x0393) )
"U+0039 DIGIT NINE " + (PrintProperties "9")
"U+00B2 SUPERSCRIPT TWO " + (PrintProperties $([Char] 0x00B2) )
"U+00BC VULGAR FRACTION ONE QUARTER " + (PrintProperties $([Char] 0x00BC) )
"U+0BEF TAMIL DIGIT NINE " + (PrintProperties $([Char] 0x0BEF) )
"U+0BF0 TAMIL NUMBER TEN " + (PrintProperties $([Char] 0x0BF0) )
"U+0F33 TIBETAN DIGIT HALF ZERO " + (PrintProperties $([Char] 0x0F33) )
"U+2788 CIRCLED SANS-SERIF DIGIT NINE " + (PrintProperties $([Char] 0x2788) )

Technorati Tags: PowerShell,scripts,PowerShell scripts,System.Globalization.CharUnicodeInfo

Show-CalendarAlgorithm.ps1

Anonymous — Mon, 31 Oct 2011 05:00:00 GMT

<#
.SYNOPSIS
This script re-implements an MSDN Sample showing the
CalendarAlgorithmType enumeration.
.DESCRIPTION
This script creates there calendars and displays
algorithm type,
.NOTES
File Name : Show-CalendarAlgorithm.ps1
Author : Thomas Lee - tfl@psp.co.uk
Requires : PowerShell Version 2.0
.LINK
This script posted to:
http://www.pshscripts.blogspot.com
MSDN sample posted to:
http://msdn.microsoft.com/en-us/library/system.globalization.calendaralgorithmtype.aspx
.EXAMPLE
#>
# Helper function
Function Display{
Param ([System.Globalization.Calendar] $c)
$name = $c.ToString().PadRight(50, '.')
"{0} {1}" -f $name, $c.AlgorithmType
}
## Start of script
# Create three new calendars
$grCal = new-object System.Globalization.GregorianCalendar
$hiCal = new-object System.Globalization.HijriCalendar
$jaCal = new-object System.Globalization.JapaneseLunisolarCalendar
# Display them
Display($grCal);
Display($hiCal);
Display($jaCal);
[enum]::GetNames([System.Globalization.CalendarAlgorithmType])