Scheduler.log "There is no address defined for site"

If the SMS Site is removed from the hierarchy and there are Jobs still in the Scheduler.box, you will get an error in Scheduler.log "There is no address defined for site".

Even though you remove the site and run the preinst /deljob:sitecode command you may get this error.

Here is my solution

•   Create a folder on another computer and share it with the name SMS_SITE.

•    Create an address (Standard Sender Address) using the site code of the removed site           (also seen in the error message)
•  For the Site Server Name use the name of the machine where the share has been created  
•  Make sure the site server has the correct permissions to connect and write to the share,     or define an account that is to be used

After a while some files will appear in the new folder, leave for a few days, then remove the files and the share. If there are no more error messages in the Sched.log remove the address for the old site

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)