Monthly Archives: December 2012

[Step-by-Step] Migrating SCCM 2007 to SCCM 2012

This post will concentrate on migrating Systems Center Configuration Manager 2007 to SCCM 2012. Since SCCM 2007 cannot do a in-place upgrade, Microsoft has provided a great migration tool, which I will be using for this post.


  • Our SCCM 2007 site server is named “sccm2007-server” and our SCCM 2012 site server is named “sccm2012-server”.

Configure SQL

  1. Connect to your sccm2012-server VM and open “Windows Firewall settings”.
  2. Turn off your firewall.
    turn firewall off
  3. Open “Sql Server Configuration Manager” and click on the drop down box for “SQL Server Network Configuration”. For the “Protocols for MSSQLSERVER” option, enable “TCP/IP”.
  4. Input the sccm2012-server ip address and “1433” for the “TCP Port”.
    configure tcpip

Configure Firewall Rules

  1. Open “Windows Firewall with Advanced Security” on your sccm2007-server.
  2. Right click on “Inbound Rules” and select “New Rule…”.
  3. A menu will be thrown called “New Inbound Rule Wizard”. Choose “Custom” for the rule type to be made and hit “Next”.
  4. The next menu will be called “Program”, leave the values to default and hit “Next”.
  5. The next menu will be called “Protocol and Ports”, leave the values to default and hit “Next”.
  6. The next menu will be called “Scope”. Under the second section in this menu, select “These IP addresses:”. Click the “Add” button that appears on the right and a new menu will open. Under “This IP address or subnet:” input the IP address of your sccm2012-server. Hit “Ok” and “Next when finished.
  7. The next menu will be called “Action”, leave the values to default and hit “Next”.
  8. The next menu will be called “Profile”, leave the values to default and hit “Next”.
  9. The next menu will be called “Name”, give the rule a name like “sccm2007-server to sccm2012-server” and hit “Finish”.
  10. Repeat these steps on the sccm2012-server. For Step 6, be sure to add the IP address of the sccm2007-server.
  11. In the end your firewall rules, for both servers will look like this.

Specify Source Hierarchy

  1. On your sccm2012-server open “Systems Center 2012 Configuration Manager” and click on “Administration”.
  2. Expand “Migration” and click “Source Hierarchy”. The top main menu will change. Choose the “Specify Source Hierarchy” option.
  3. This will throw a menu called “Specify Source Hierarchy”. Enter your sccm2007-server name followed by your domain in the box under “Top-level Configuration Manager 2007 site server:”.
  4. In the drop down menu called “Set…”, next to “User Account:”, click “New Account”.
  5. This will bring up a new menu called “Windows User Account”. Input a user account that has read access to the sccm SQL database.
  6. Hit “Verify >>” and the menu will be expanded. In the expanded section you will see a button called “Test Connection”. Press this button when all of your information is correctly inputted.
  7. If the connection was successful, a menu will pop up stating “The connection was successfully verified”.
  8. When everything is set up hit “Ok” and you should be done specifying the Source Hierarchy.
  9. A menu called “Data Gathering Status” will pop up. This will automatically collect data from the sccm site.

  10. When its complete, the source properties will be updated in the SCCM operations console.

Create a Migration Job

  1. Navigate to “Migrate” under Migrate and click on “Create Migration Job”.
  2. A menu will appear, name the MIgration job, set the “Job Type” and give it a description(optional).
  3. The next menu will allow you to choose the objects to be migrated. Hit “Next” when you are done with your selection.
  4. The next step will ask you to assign the website you are migrating to.
  5. The next step lets us set the “Security scope”. I’ve checked default and hit next.
  6. The next step will allow you to review you migration settings, hit next.
  7. The next screen will allow you to set the time when the migration will happen. Set the Migration to “Overwrite all objects”.
  8. The next step will ask you to “Confirm your Settings”, double check them and hit next.
  9. Hit next and the migration will begin and finish (rather quickly for me). You will see a “Successful migration screen”. Hit “Close” to finish.
  10. Navigate to “Migration Jobs” once again and you will see the migration running.
  11. When the migration finishes, you should be done!

Please leave any questions, comments or concerns!

Leave a comment

Posted by on December 31, 2012 in Uncategorized


Install Dell MD Storage vCenter Plug-in

This blog post is about integrating vCenter with your Dell PowerVault storage array. This particular software enables storage system management and configuration avoiding having to flip back and forth from MD Storage Manger (array management software for MD storage arrays). This is a relatively painless process that doesn’t take long to setup.

Getting Started

Create a Service Account

Note: We have an Organizational Unit called “Service Accounts” that handles these type of accounts.

  1. Open Active Directory and navigate to your “Service Account” OU (or where ever you would like to make the account). Right Click the folder -> “New” -> “User”.
  2. Name the new user something like “service-dell_utils” and give the user a password.

Starting the Installation

  1. Open the  “dell-utils” VM and navigate to the plug-in installer (vcenterInstaller.exe).
  2. InstallAnywhere will start and finish. The vCenter Plugin main screen will appear. Select your language and hit “ok”.
  3. The introduction screen will appear, hit “Next”.
  4. The Copyright Statement will appear, hit “Next”
  5. Accept the terms and agreements and hit “Next”.
  6. A menu named “Pre-Installation Summary” will appear, confirm your settings and hit “Next”.
  7. A window will appear during the installation named “VMware ESX Provider”. This will inform you that a “VMware ESX Provider” has been deployed to your program files. This application will have to be manually installed on your ESX\ESXi Server to support SAS capabilities. Ignore this if using iSCSI.
  8. The Setup will finish. A menu will appear named “Enter the SSL and Non SSL Jetty Port Numbers”. Leave these values to default and hit “Next”.
  9. The next menu will ask you to enter the IP Address of the server that you are installing the plugin on. Input the IP address of your dell-utils VM and hit “Next”.
  10. The next menu will ask you to enter the IP Address of your vCenter server. Input the IP address in the box and hit “Next”
  11. The next step will ask for the administrative login to your vCenter server. Input the “service-dell_utils” account credentials.

Enable the Plug-In

  1. Open your vCenter Client and navigate to “Plug-ins” -> “Add Plugin”. Right click the “Dell MD Storage Array” item and choose “Enable”.
  2. Now that the plugin is enabled, navigate to “Home” and you will see your plugin under “Solutions and Applications”
  3. Click on the plugin icon and this should bring you to a screen that states “User is not authorized to use this plug-in”.

Configure Administrative Permissions

  1. Under the “View” tab, expand “Administration” and click on “Roles”.
  2. Click “Add Role” in the upper left. A menu will appear. Give the new role a title like “Storage Administrator”. Under Privileges, expand “Storage Administrator” and uncheck “Read Only”.
  3. Navigate to “Hosts and Clusters”, right click on the top “vCenter” cluster and hit “Add Permissions”.
  4. A menu called “Assign Permissions” will appear. On the right under “Assigned Role”, choose “Storage Administrator” in the drop down box.

Now you are ready to configure a Dell MD Storage Array.

Any Questions or comments, please feel free to comment!

1 Comment

Posted by on December 27, 2012 in Uncategorized


Deploy Configuration Manager 2012 Client Using a Startup Script

This post is about deploying the Configuration Manager 2012 client using a startup script. This is a heavily modified script of the original made by Jason Sandy which can be found here.


  • The script and xml readme can be found here.

New Features

  • For Windows XP and 2003 machines, the certificate auto-enrollment legacy hotfix (KB968730) can now be installed by the script. New options are defined in the xml file for the legacy hotfix.
  • Input arguments are more flexible.
  • Logs can be copied to a central share.
  • Additional SCCM client arguments can now be specified in the XML.
  • CU’s now scan and install properly according to architecture.

What does it do?

  • The script will:
    • Install the SCCM 2012 client.
    • Maintain the health of the SCCM client.
    • Install Client hotfixes.
    • Install certificate enrollment hotfixes.
  • This script does not fix WMI problems at this time. That’s a feature we’re still working on.

How do I use it?

  • Make a Group Policy Object in the OU of your choice, name it “Deploy SCCM Client”. In the GPO under “Startup” scripts assign:
  • For name: Enter the path of where your script is stored plus the script name.
  • For parameters: Enter “/config:” and the path to the xml file.
    GPO settings

XML Options

See the github readme for additional options available in this version of the script.


Leave a comment

Posted by on December 17, 2012 in Uncategorized