Tuesday, October 5, 2010

SQL Reporting Services: SRS

SQL Reporting services have some benefits over the current reporting solution:

  • Provide best in class reporting capability by integrating SQL Reporting Services, with the leading change and configuration management product: SCCM 2007
  • Enable Ad-hoc reporting - Make it easy for both SCCM administrators, and non administrators to find the information they need to make the right decisions for their business
  • Support alternative databases as the reporting database, such as a replicated or backup database
  • Allow custom report creation via a report authoring wizard.
  • Enable report browsing and viewing via the SRS Report Viewer.
  • Take advantage of rendering in all supported SRS formats, report caching, and subscriptions.

This article will explain setting up SRS with Configuration Manager based on SQL 2008. I’ve taken most of the steps from this article (many thanks to Michael Wiles). I’ve added some screenshots and applied it to SQL 2008, while the original article discusses SQL 2005. If you need more background info on SRS check out that link.

Install and configure SQL Reporting Services in SQL 2008

 

Be sure to check Reporting Services as part of your SQL installation

image

At step 21 of this part of this guide the setup provides you with three choices:

  • Native mode default configuration
  • SharePoint mode default configuration
  • Unconfigured Reporting Services installation

You should select Unconfigured Reporting Services installation at this point.

After the installation finishes you should configure SRS for the use with Configuration Manager 2007.

1. In the start menu select Microsoft SQL Server 2008 / Configuration Tools, then click Reporting Services Configuration Manager.

2. In the Reporting Services Configuration Connection select the Server Name and the Report Server Instance, then select Connect.

image

3. In the Report Server Status verify that the Service Status is set to Running. If it is not, click Start, and then click Apply.

image

4. Select Web Service URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default ReportServer). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.

image

5. Select Database, select Create a new report server database in the Report Server Database Configuration Wizard and click Next

image

6. Select the Database Server Name and Authentication Type that matches your SQL server and credentials.

image

7. Supply the Database Name and Language. Be sure to select Native Mode for Report Server Mode. Click Next.

image

8. Select the proper credentials from the drop list for Authentication Type

image

9. In the Summary screen review your settings and Click Next.

image

10. Review your database in the Report Server Database screen.

image

11. Select Report Manager URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default Reports). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.

image

12. Email settings are not mandatory to setup, but can be configured appropiately if necessary.

13. Execution Account is necessary to configure if you will be running unattended reports. Optionally apply credentials and Click Apply.

20. Click Exit to close Reporting Services Configuration Manager.

Configure Configuration Manager 2007

SQL Reporting Services need the configuration of a Reporting Services Point role.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code>-<site name> / Site Settings / Site Systems.

2. In this guide I will add the reporting services point site role to the existing site system. Right-click the site system name, and click New Roles. On the General page of the New Site Role Wizard, configure the general settings for this site system, then click Next.

image

3. On the System Role Selection page of the wizard, select Reporting Services point (don’t select Reporting Point by mistake, which is the traditional reporting functionality), then click Next.

image

5. On the Reporting Services Point page, specify the folder that will be created on the report server to contain the SQL Reporting Services reports used in Configuration Manager and then click Next.

image

6. Review the information shown on the Summary page, then click Next.

7. Click Close to exit the wizard.

8. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services, and expand the node.

9. Right-click the reporting services point server you want to configure, then click Properties.

10. On the Data Source Settings tab of the Report Server Properties dialog box, specify the Configuration Manager 2007 database server and database name (not the one create earlier for reporting!) to be used as the data source for SQL Reporting Services reports. Click the test button to verify that you have correct data entered.

image

11. On the Data Source Authentication tab of the Report Server Properties dialog box, specify the credentials used to access reports on the report server. I’ve use Windows Integrated Security here.

image

12. On the Data Source Security tab of the Report Server Properties dialog box, specify permissions for the users who have access to the data source specified in the Data Source Settings tab.

image

13. On the Security tab of the Report Server Properties dialog box, specify the users who have access to the selected report server.

image

14. Click OK to close the Report Server Properties dialog box.

Import standard reports in Reporting Services

The last step in configuring SRS for Configuration Manager 2007 is to convert the standard reports to Reporting Services reports.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services

2. Right-click the Reporting Services server that the standard reports will be copied to, then click Copy Reports to Reporting Services.

image

3. On the Data Source Settings page of the Copy Reports Wizard, specify the Configuration Manager 2007 database server and database name from which to copy the reports. Click Next.

image

4. On the Data Source Authentication page of the Copy Reports Wizard, choose the authentication method required to run the copied reports on the reporting point server. Click Next.

image

5. On the Select Reports page of the Copy Reports Wizard, select the reports you want to copy to the reporting services point. Select Overwrite existing reports if you want to overwrite any reports that already exist on the reporting services point. Click Next.

image

6. On the Security page of the Copy Reports Wizard, specify which users can access the copied reports and the roles they must belong to. For more information about the options on this page, see Report Server Properties: Security Tab. Click Next

image

7. On the Summary page of the Copy Reports Wizard, review the reports that will be created, and then click Next.

image

8. After the reports are copied, click Next.

image

9. On the Confirmation page of the Copy Reports Wizard, review the information, and then click Close to exit the wizard.

Reports are now available Site Database / Computer Management / Reporting / Reporting Services / <Site Server> / All Reports

image

To run a particular report just Right Click the report and select Run.

image

Popular and useful tools for ConfigMgr 2007

  • SCCM Right Click Tools
  • SCCM Client Center
  • OSD++
  • SMSMap
  • SCCMAutoDoc
  • SCCM 2007 SDK
  • SCCM-Tools.com
  • BitsAdmin
  • WMI Administrative Tools
  • WMI Diagnosis Utility

 

 

http://www.petervanderwoude.nl/post/The-best-(free)-tools-for-ConfigMgr-2007!.aspx

Step by Step 4 part guide to Deploying Windows 7 Enterprise.

Deploy Windows 7 part 1.
Build and Capture
Part 1 is the longest part of the 4 part guide and covers the steps required to successfully Build and Capture Windows 7 RTM. It was tested successfully on both X86 and X64 Enterprise RTM releases.
Step 1. get the ISO
Step 2. Add Operating System Install Package
Step 3. Create Distribution Point for the Image
Step 4. Update Distribution Point
Step 5. Create the Build and Capture Task Sequence
Step 6. Advertise the Build and Capture Task Sequence
Step 7. Add a system to the Build and Capture 7 collection
Step 8. PXE boot the newly added Windows 7 client
Deploy Windows 7 part 2.
Add the captured WIM file
Step 1. Add the Captured Wim file as an Operating System Image
Step 2. Distribute the Captured WIM file
Deploy Windows 7 part 3.
Create a new Task Sequence
Step 1. Create a new Task Sequence
Deploy Windows 7 part 4.
Advertise the Task Sequence
Step 1. Advertise the Task Sequence
Step 2. Last Actions
enjoy !
cheers

SCCM Index : End- End

SCCM Index from windows noob

 

http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/

A legacy network adapter : Hyper - V

A legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network-based installations because it includes the ability to boot to the Pre-Boot Execution Environment (PXE). The legacy network adapter is not supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition."

 

image

 

then you can see as below

 

image

Hyper – V : Installing a Legacy Network Adapter

Installing a Legacy Network Adapter.
(Legacy Adapters aren't supported in Windows Server 2003 64-bit or Windows XP 64-bit)
1. Make sure your Virtual Machine is shutdown.
2. Right-click the Virtual Machine in Hyper-v select Settings.
3. Select Add Hardware.
4. On the Add Hardware page select Legacy Adapter.
5. Then click Add.

Monday, October 4, 2010

OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause:  This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.