Migrate SCCM 2007 SSRS Reports to SCCM 2012 Reports

This blog post discuss about how to migrate reports ,download,upload your custom reports to Configmgr SSRS folder

Download the tool from https://code.google.com/p/reportsync/

If you want to download the Reports (.RDL) files from your SSRS server (Configmgr 2007 or  2012),enter the sourceURL ,User hat has permissions to connect to SSRS,Password in Source URL Web Service and click on Load.

Select the report that you want ,provide the local path to store these reports (.RDL files) and click on Download.

Each category what you see in this tool will be created as Folder in yours local Path.
You can also try to upload your customized reports to Destination server ,sync and do other functions with this tool

About Heartbeat Discovery

The default schedule for Heartbeat Discovery is set to every 7 days. I typically set this down to every 1 day and know others do it even more often.  I would never recommend setting this to less than 1 or 2 hours except in very small environments – there isn't really any value in doing so anyway as nothing in the above list normally changes that frequently.

The Heartbeat Discovery also serves as a “keep alive” or “yes I am alive” message from the client to the site server. Based on this, the Clear Install Flag and Delete Aged Discovery Data maintenance tasks perform their jobs. Note that the Delete Inactive Client Discovery Data  does not directly use the heartbeat time. Instead, Client Status Reporting (available in R2 and R3), uses the last heartbeat time along with last hardware inventory, last software inventory, and last policy polling time to determine if a client is inactive. Once a client is marked inactive by Client Status Reporting, it is then subject to the Delete Inactive Client Discovery Data task.

Whenever heartbeat discovery agent runs on the machine, it provides us the below information

•                     Is the client installed?

•                     Client type (Legacy, Advanced, or Device)

•                     Client version

•                     NetBIOS Name

•                     Character encoding used by the client

•                     Default system locale identifier (typically representative of the client’s language)

•                     Date and time of the DDR

•                     Date and time of last DDR

•                     Short name of system

•                     Currently logged in (interactive) user

•                     FQDN of system

•                     IP Network ID

•                     Platform ID (this is an encoding of the OS version)

•                     AD Site Name

•                     IP Address(es)

•                     MAC Address(es)

•                     Domain name

•                     Assigned (Primary) Site

•                     Hardware ID

•                     Identifying number (of the computer system)

•                     Product name (of the computer system)

•                     UUID (of the computer system)

•                     Version (of the computer system)

How To Remove Orphan Distribution Points

 Before Remove the distribution Point from the Site System, must remove the packages from the DP, But sometimes we forgot to do this often.

And then they end up with errors from each package because SCCM can´t access the server and it can´t delete the package etc (distmgr.log). It will also still list the DP under each package.

The only way is to remove the entry from the SQL Database,

Please keep in mind that manually editing the database is unsupported!

1. Backup the ConfigMgr database.

2. Find the entries for the DP package share:

Queries for finding information that needs to be delete later on.

Select * from pkgservers where NALpath like '%\\<servername>%'

Select * from pkgstatus where pkgserver like '%\\<servername>%'

Select * from contentdpmap where serverpath like '%\\<servername>%'

Select * from DPinfo where servername like '%<servername>%'

3. Delete any entries from any of the above tables that point to the nonexistent share:

Queries for deleling information about the DP that was removed earlier.

Delete from pkgservers where NALpath like '%\\<servername>%' 

Delete from pkgstatus where pkgserver like '%\\<servername>%'

Delete from contentdpmap where serverpath like '%\\<servername>%' 

Delete from DPinfo where servername like '%<servername>%'

You can also use a SDK script when the DP is alive - http://blogs.msdn.com/rslaten/archive/2006/03/01/Removing-a-retired-DP-from-all-your-packages.aspx

SCCM 2012 Client Upgrade Package Distribution Failed

Whenever you setup a new distribution point, the system will automatically distribute 2 packages to the distribution point.

          1. Configuration Manager Client Package

          2. Configuration Manager Client Upgrade Package

But somehow the Configuration Manager Client Upgrade Package failed to distribute to the distribution point. The upgrade package is hidden, hence unable to redistribute the upgrade package like normal package. Therefore, we have to trick the system to redistribute the packages.

Resolution:-

1. Open an empty notepad and save it as client.acu

2. Copy the client.acu to the inboxes\hman.box folder at the top-level site

3. Monitor the hman.log to check whether the Client Upgrade package gets updated

WDS and DHCP are running in the same SCCM Server

WDS service will not start, since DHCP and WDS both will use the same port 67 by default.

To get around this the following registry change needs to be made (UseDHCPPorts = 0)

Monitored PXEControl.log to ensure PXE was responding to tests

         
 If PXE boot still didn't work run the below command
Initialize the WDSServer (wdsutil /initialize-server /reminst:G:\RemoteInstall) 
NOTE: Adjust the G:\remoteinstall location to reality in your environment

Next you need to run the following command for the registry change made in above step
 to take affect

SCCM 2007 - Task Sequence Error 0x80004005 & NO MP Certificates

When you get the below error it might be a problem with the boot image (If you were using a boot CD for image deployment) or problem with the Management Point

It’s very advisable to investigate the smsts.log files to troubleshoot task sequence errors. The log file is located on different locations depending on the task sequence process. My reference machine rebooted even before format so I needed to get my log file from the Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log. You need to press F8 during WINPE to get command line abilities and copy your log file to another destination.  Make sure that “Enable command support” is enabled in your boot image properties ( Operating system deployment – Boot images – right click your boot image – properties –  WINPE tab)

Solution - Create a new boot image & if still No MP Certificates error occurs re-install the Management Point

Supported Client Version of App-v in SCCM 2012

Before the migration of SCCM 2012 you should check the App-v client version on your environment, below are the App-v version details

App-v Client Version	Support Details
4.5.0.15341 (App-V 4.5 HF03 Jan 2009)	Not Supported in SCCM 2012
4.6.0.1523 (App-V 4.6 RTM)	Not Supported in SCCM 2012
4.6.0.20200 (App-V 4.6 All Languages)	Not Supported in SCCM 2012
4.6.1.20870 (App-V 4.6 SP1)	Not Supported in SCCM 2012
4.6.2.24020 (App-V 4.6 SP2)	Supported in SCCM 2012
4.6.2.30111 (App-V 4.6 SP2 HF03)	Supported in SCCM 2012
4.6.3.24870 (App-V 4.6 SP3)	Supported in SCCM 2012
4.6.3.25111 (APP-V 4.6 SP3 HF01)	Supported in SCCM 2012

The below SQL query will help you to find the App-v version details on your site

SELECT     dbo.v_R_System.Netbios_Name0, dbo.v_R_System.User_Name0, dbo.v_R_System.AD_Site_Name0, dbo.v_GS_OPERATING_SYSTEM.Caption0,

                      dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0,dbo.v_GS_ADD_REMOVE_PROGRAMS.Version0

FROM         dbo.v_R_System INNER JOIN

                      dbo.v_GS_OPERATING_SYSTEM ON dbo.v_R_System.ResourceID = dbo.v_GS_OPERATING_SYSTEM.ResourceID INNER JOIN

                      dbo.v_GS_ADD_REMOVE_PROGRAMS ON dbo.v_R_System.ResourceID = dbo.v_GS_ADD_REMOVE_PROGRAMS.ResourceID

                      where

                   

                      dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 like 'Microsoft Application Virtualization Desktop Client'

If the client App-v is not upgraded, you will receive the below error on ccmsetup.log