my personal blog about systemcenter

Archive for September, 2012

 

Service Manager 2012 SP1 installs a Operations Manager agent on the Service Manager

 

image

So instead of having to rely in agentless monitoring of the Service Manager management servers we now have the agent supplied in the box , not that the install path is also in service manager not in operations manager

 

image

 

On the operations Manager Server we need to ensure that manual agent install is permitted

 

image

In the control panel on the service manager server add the management group that use used for operations manager , and you will see the agent in operations manager after you apply the changes

One of the many new features in Windows Server 2012 is Failover DHCP scopes without having to use Windows Failover Clustering , this post will setup a shared scope between 2 server where both DHCP servers are activ

 

image

One one of the DHCP server use Configure Failover

 

image

If there is mutiple dhcp scopes select the scopes you want to replicate to the 2nd dhcp server

image

Add the partner dhcp server

image

Load Balancing will ensure that each dhcp server resonds to client request based on mac address hash

 

http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx

 

image

The DHCP server polls each other every 5 minutes to ensure that each know how many addresses are available

With the release of System Center 2012 SP1 Beta , Microsoft added the feature to use Windows Azure Cloud for data storage.

To us the Azure for backend you need a account there is a free 300gb account for testing avaialble at

http://www.windowsazure.com/en-us/home/features/online-backup/ , also Data Protection Manager must run on Windows Server 2012.

This post will just cover the basics there will be follow up on whats supported when time permits Smiley , and we still dont know the cost yet Smiley , performance and a bunch of other stuff needs to be tested its a great start.

 

image

Install the Windows Azure Online Backup agent

image

Voila.

 

image

To use the Azure as backend you must create a user , so go to the Windows Azure Active Directory Portal

image

Create a user for connecting the Data Protection Manager server with Azure , not sure if one is needed pr server but for testing purpose i made a dedicted one

image

The accoutn needs to be global administrator , and you need to logon to the portal to change password after the user have been created

image

Go to management and register a online protection

image

Enter username/password from the earlier created user

image

Set any throttle policy

image

During restore you need staging space so this needs to be added in the design of DPM as the disk space is local to the dpm server

image

Data is compress and encrypted before being shipped off to Windows Azure , so DO NOT loose the passphrase , you will not be able to recover if the dpm server is “gone”

image

Sucess Smiley

 

image

And we can see our Azure Subscription in the DPM interface directly , time for the first cloud backup

 

image

Lets create a protection group , notice the new shiny graphics

image

For testing purpose we just add the C: from one of the Hyper-V nodes

image

Select both cloud and short term protection

image

Select the drive we want protected in the Azure Cloud

image

7 day protection and one synchronization a day

image

Data Protection Manager = Sucess

image

image

And we can see our initial replication creation to disk work its magic.

image

The scheduled job will kick in later but i would like to use the new create recovery point with “online protection”

 

 

image

image

and we know have data moving to the cloud ,

image

So now when we select data we have a additional recovery point

image

And we can see that we recovery to local and then from staging to target.

image

dcpromo went on holliday after Windows Server 2008 R2 so to promte a server to domain controller we need to use powershell or server manager , so with 12 years with dcpromo i exept to type that a few times more until i remember its gone away

 

 

image

Head to server manager and add role on local server

 

 

image

Select Active Directory Domain Services

 

image

In task details select Action Promote this server to a domain controller

 

image

As this is the start of a new forest we need to add the forest and specifi root doman name

 

image

 

One VERY handy new feature most places in Windows Server 2012 ish the view script command

 

#
# Windows PowerShell script for AD DS Deployment
#

Import-Module ADDSDeployment
Install-ADDSForest `
-CreateDnsDelegation:$false `
-DatabasePath “C:\Windows\NTDS” `
-DomainMode “Win2012” `
-DomainName “internal.systemcenterdemo.dk” `
-DomainNetbiosName “INTERNAL” `
-ForestMode “Win2012” `
-InstallDns:$true `
-LogPath “C:\Windows\NTDS” `
-NoRebootOnCompletion:$false `
-SysvolPath “C:\Windows\SYSVOL” `
-Force:$true

And we get the syntax for creating a new forest from powershell instead of using 10ish mouse clicks

 

 

image

And we know have a functional forest Smiley