Since it’s a freshly installed Windows 7 client, we dont have to bother about userprofiles and so on.. we’ll save that for later

Joining the domain is done through WMI. Just create a new Object containing the Win32_ComputerSystem WMI object and call the JoinDOmainOrWorkGroup() method.

function JoinDomain ([string]$Domain, [string]$User, [string]$Password ) {

	$DomainUser = $Domain + "\" + $User
	$OU = $null

	$ComputerSystem = gwmi Win32_ComputerSystem

	$ComputerSystem.JoinDomainOrWorkGroup(
		$Domain,
		$Password,
		$DomainUser,
		$OU,
		3
	)
}

Here’s an example on running the function.

PS > JoinDomain PowerShell.nu migaccount Password1

And voila! the client shuts down and on Startup, It’ll have joined the new domain.

]]> http://www.powershell.nu/2009/06/05/joining-a-windows-7-client-to-a-domain-through-powershell/feed/ 2 http://www.powershell.nu/2009/06/05/write-stickynote/ http://www.powershell.nu/2009/06/05/write-stickynote/#comments Fri, 05 Jun 2009 16:30:03 +0000 Niklas Goude http://www.powershell.nu/?p=741 Here’s a fun script that uses the new “Sticky Notes” in WIndows 7.

The script is based on a simple function that uses the SendKeys() method through the Wscript.Shell COM object. This is a nice example on how you can handle COM objects through PowerShell.

I’ve also included an if statement that checks if StickyNotes is active. If that’s the case, the text will be started in a new StickyNotes.. note..

Anyway, here’s the function.

function Write-StickyNote ([string]$Text) {

	if (gps | Where { $_.ProcessName -match "stikynot" }) {

		$StickyNote = $True
	}

	$Wscript = New-Object -Com Wscript.Shell
	[void]$Wscript.Run("stikynot.exe")
	start-sleep 1

	if ($StickyNote -eq $True) {

		$Wscript.SendKeys("^n")
	}

	$Wscript.SendKeys($Text)
}

And here’s an example on running the function.

PS > .\Write-StickyNote.ps1 "Hello from PowerShell.nu"

Click here to download the Script

I’m hoping that alot of people share my enthusiasm regarding the Windows 7 technologies and I would like to share my Beta tests with the Microsoft Community. I’m aware that a few commands and techniques may vary from the final Release so the following posts might not be accurate when the final build of Windows 7 / 2008 R2 are released. I will try to keep these posts up to date and follow Microsfts development of Windows 7 and Windows Server 2008 R2.

Scenraio

You have a Windows 2003 Active-Directory Environment that you want to Updgrade / migrate to a Windows 2008 R2 environment. Microsoft have a great tool called ADMT (Active Directory Migration Tool) which allows you to perform the appropriate steps when migration from Windows 2003 to Windows 2008. But since this is a PowerShell Blog, I’m going to show examples on doing all these steps through PowerShell. I’m planning on showing the following steps:

Windows 2003

• Scripting up a Active-Directory Test Environment through PowerShell
• Adding Ou Structure using Powershell
• Adding Users through PowerShell
• Adding Computers through PowerShell
• Adding Groups Through PowerShell
• Adding Group Membership Through PowerShell
• Adding HomeFolder Through PowerShell
• Joining a Windows 7 Client to a Domain through PowerShell

Windows 2008 R2

• Gathering information from a 2003 Active Directory Domain through PowerShell
• Migarting OU Structure to a Active-Directory 2008 R2 Server Through PowerShell
• Migarting Users to a Active-Directory 2008 R2 Server Through PowerShell
• Migarting Computers to a Active-Directory 2008 R2 Server Through PowerShell
• Migarting Groups to a Active-Directory 2008 R2 Server Through PowerShell
• Migarting Group Membership to a Active-Directory 2008 R2 Server Through PowerShell
• Migrating HomeFolders to a Active-Directory 2008 R2 Server Through PowerShell
• Migrating a Windows 7 Client to a Active-Directory 2008 R2 Server Through PowerShell

Note that all steps are built from a test environment and may require slight adjustments to fit your environmnent.

]]> http://www.powershell.nu/2009/04/11/part-00-migrate-from-windows-server-2003-to-windows-server-2008-r2-and-windows-7-using-powershell/feed/ 0