Apr 30

VGX.DLL Unregister Workaround for SCCM(2963983)

I am sure by now most people have heard of the IE all version vulnerability.   If you have not spend some time here.  Word on the street is the fix may not be around for several months so a workaround is in order.  I did not want to disable Flash(how would users waste time all day), so the next best thing is unregistering the VGX.DLL.   I put together a quick VBscript that can be imported into SCCM(all versions) and deployed to all Windows versions Servers/Workstations.    I know MS recommends doing this through GPO but I want some reporting on the change and have the ability to re-trigger on my schedule.

On a 64bit Windows OS the script unregisters the 32bit and 64bit VGX.dll.

On a 32bit Windows OS the script unregisters the 32bit VGX.dll.

The script can be run on all Windows systems in your environment, so far I have tested on 2008,2008r2,2003 and Windows 7.

Apr 30

SCCM 2012 Right Click Tools 1.4 install issue

I assume that everyone that uses SCCM has used different right click tools. After upgrading to 2012 I was lacking a good set of right click tools.  I searched the web and found these: http://myitforum.com/myitforumwp/2012/05/07/config-manager-2012-right-click-tools/

These have all the same tools as the 2007 version.  I installed these but ran into an issue that was not documented.   If you are having the same issue I hope this resolves it for you.  Once resolved these tools are the must have addition have any SCCM Admin.

Symptom:  Right Click tools 1.4 installed, show up in configuration manager console but when any tool is executed nothing happens.

Fix:

  1. Go to the c:program filesSCCMConsoleExtensions
  2. Right click on the scripts, go to properties and unblock
Mar 19

Migrating SCCM 2007 to SCCM 2012 – Part 4 migrations begins

This is the checklist/worksheet I am using for the migration.  I will update this as the install progresses.  This checklist came from http://technet.microsoft.com/library/gg682006

 

The Sp1 Pre-Req check for SCCM 2012 is buggy I got different results each time I ran it. I finally manually checked everything then started the install.   Migration of collections has started.   Working with a few clients on both sites now.

Step 

Results 

Notes

Assess the current environment.

Current Environment looks good there are some items that I am removing

Review the functionality and changes that are available with the version of System Center 2012 Configuration Manager that you use, and use this information to help you design your destination hierarchy.

Will go into details on these post upgrade.  Right now it is like for like

Determine the administrative security model to use for role-based administration.

There will be a full post on the Security model post uprade

Assess your network and Active Directory topology

Getting rid of seconday and replacing with DP

Finalize your destination hierarchy design.

Single Site server and a handfull of DPs.  New Site code

Install a stand-alone primary if you do not plan to use a central administration site.

Map your hierarchy to the computers that you will use for sites and site servers in the destination hierarchy.

Server10 – SCCM 2012

Server11 – SCCM SQL Server

Server12 – New distribution Point

Server8 – Upgraded Distribution Point

Plan your object migration strategy.

 completed

Plan your client migration strategy.

 completed

Plan your client migration strategy.

 completed

Plan for the completion of migration from the source hierarchy.

 completed

Identify the computers to use in the destination hierarchy.

See Above

Create your destination hierarchy.

created server10,Server11 and Server 12

If you want to migrate information that is related to software updates, configure a software update point in the destination hierarchy and synchronize software updates.

 skipping updates

Install and configure additional site system roles in the destination hierarchy.

 added AppV

Verify operational functionality in the destination hierarchy.

 all items work except reporting services.  Will configure as migration is working

-All Pre Items ABOVE

Enable migration in the destination hierarchy.

Sites linked and Migrations of collections have started.

When the source hierarchy runs Configuration Manager 2007 SP2, select and configure additional sites in the source hierarchy.

Configure distribution point sharing.

Create and run migration jobs to migrate objects associated with the clients in the source hierarchy.

Migrate clients to the destination hierarchy.

Upgrade shared distribution points.

Complete migration.

Mar 10

Migrating SCCM 2007 to SCCM 2012 – Part 3 The Plan With a checklist

This is the checklist/worksheet I am using for the migration.  I will update this as the install progresses.  At this point I have brought up the 3 new servers and I am in the process of installing the SCCM 2012 environment.   This checklist came from http://technet.microsoft.com/library/gg682006

Step 

Results 

Notes

Assess the current environment.

Current Environment looks good there are some items that I am removing

Review the functionality and changes that are available with the version of System Center 2012 Configuration Manager that you use, and use this information to help you design your destination hierarchy.

Will go into details on these post upgrade.  Right now it is like for like

Determine the administrative security model to use for role-based administration.

There will be a full post on the Security model post uprade

Assess your network and Active Directory topology

Getting rid of seconday and replacing with DP

Finalize your destination hierarchy design.

Single Site server and a handfull of DPs.  New Site code

Install a stand-alone primary if you do not plan to use a central administration site.

Map your hierarchy to the computers that you will use for sites and site servers in the destination hierarchy.

Server10 – SCCM 2012

Server11 – SCCM SQL Server

Server12 – New distribution Point

Server8 – Upgraded Distribution Point

Plan your object migration strategy.

Plan your client migration strategy.

Plan your client migration strategy.

Plan for the completion of migration from the source hierarchy.

Identify the computers to use in the destination hierarchy.

See Above

Create your destination hierarchy.

created server10,Server11 and Server 12

If you want to migrate information that is related to software updates, configure a software update point in the destination hierarchy and synchronize software updates.

Install and configure additional site system roles in the destination hierarchy.

Verify operational functionality in the destination hierarchy.

-All Pre Items ABOVE

Enable migration in the destination hierarchy.

When the source hierarchy runs Configuration Manager 2007 SP2, select and configure additional sites in the source hierarchy.

Configure distribution point sharing.

Create and run migration jobs to migrate objects associated with the clients in the source hierarchy.

Migrate clients to the destination hierarchy.

Upgrade shared distribution points.

Complete migration.

Mar 04

Migrating SCCM 2007 to SCCM 2012 – Part 2 The Plan

So there is no in place upgrade with SCCM 2012 from 2007.  From what I understand I need to stand a new environment up next to it and migrate components over.   I want to end up on SCCM 2012 SP1, this is what I found on technet…

For System Center 2012 Configuration Manager SP1 only, you can migrate an existing Configuration Manager 2007 SP2 infrastructure or an existing System Center 2012 Configuration Manager SP1 infrastructure to System Center 2012 Configuration Manager SP1.

That is enough for me… I will use a hybrid of the different checklists to do the migration.   I will edit this post as changes are made.

Main Source for Checklist: http://technet.microsoft.com/library/gg682006

Prerequisites for Migration(Link)

  • Support version – 2007 sp2r3 to 2012 sp1 is supported
  • Language – English
  • Configs:
    • In Destination site assign the user account to role-based administration security role of Infrastructure Administrator
    • Data Gathering Accounts create two accounts listed in above link
    • Before Migration Software Upgrate Point must be installed in new site
    • Prepare for Shared Distribution Points see Above Link

Admin checklist for migrations:

I am going to use the Technet checklist.   I will post any variations or failures as I move through it.

http://technet.microsoft.com/en-us/library/gg712683.aspx