anyweb

dude this info is good because it will help people who have this problem, (I like the fact that you show screenshots of SCCM in it's error state and include the actual errors) but I'm guessing that you didn't see this yet ? cheers anyweb

Step 2. Install Operations Manager 2007 Reporting Log on to the SCOM server with Local Administrative Permissions and run SetupOM.exe from the SCOM installation media, click Install Operations Manager 2007 Reporting when the System Center Operations Manager 2007 Setup screen appears. When the Welcome to the Operations Manager 2007 Reporting Setup Wizard appears, click Next accept the terms in the license agreement and click Next In the Product Registration screen, leave the defaults and click Next At the Custom Setup screen, make sure the location is set to D:\Program Files\System Center Operations Manager 2007 and click Next, verify that the This component and all dependent components will be installed on local disk drive is selected for both Data Warehouse and Reporting Services The installer will do a PreRequisite check and if you get any warnings you will need to read the log by clicking on View Log. (I got a warning about the amount of RAM in my SCOM server, it's a virtual machine with only 512mb ram and SCOM recommends 2GB). On the Connect to the Root Management Server screen, type the name of the Root Management Server and click Next, leave the SQL Server Database Instance settings as they are, For the Database and Log file settings, you could consider setting the Database to 5000MB (default is 1000), but as this is a lab, we shall leave it as it is..if you had your DB and LOG files stored on SAN drives it would be here that you could define their location by clicking on the Advanced button. We are just creating a lab so go with the defaults. Review the SQL server reporting services server value (leave it as is) and click next If you get the SRS validation errors then do as follows 1. COPY the ResetSRS.exe file in SupportTool folder of OM 2007 to C:\. (Of course, you can run this file in OM folder.) 2. Then open the COMMAND PROMP and change your path to C:\. 3. Type "ResetSRS.exe MSSQLSERVER" where MSSQLSERVER is your SQLINSTANCENAME. 4. Then open Reporting Services Configuration Console in your Program Menu and select Web Service Identity and on the right side click Apply. 5. Finally, reinstall your reporting service by running OMSetup.exe again. For the Data Warehouse Write Account screen, type the credentials of the Data Warehouse Write Action Account which we created in Setup Part 1 (OpsMgrDWWAA) and click Next Next we have to se the Data Reader Account so enter the credentials of the Data Reader Account which we created in Setup Part 1 (OpsMgrDRA) and click Next For Operational Data Reports, leave it on No and click next And click on Install when the ready to install the program screen appears and finally after a long install you should see the completing the operations manager reporting components setup wizard screen click Finish to exit.

Please Note: This guide is not finished yet, while you see this line you can be sure that this post is not complete. Step 1. Verify Reporting Services in SQL Note: Failure to do this step will most likely result in SRS Server Validation errors when you try to do Step 2 below. Verify that the SQL reporting Service is started, open Server Manager, Configuration, Services and check the SQL Reporting Services Service, if it is not started then start it. You can also check that these are running by opening a web browser and checking the following addresses http://localhost/Reports http://localhost/ReportServer if neither of them respond then either the reporting service is not started or you need to reinstall SQL reporting services.

yes you can do it. no problem.

you should always check the security of IIS and the entire server, I would suggest using MBSA to do this. Here is a FAQ for MBSA and you can download it from here cheers anyweb

make sure that the pc's you are trying to WOL have had a clean shutdown first, a clean shutdown is where you tell the OS to power down using the start menu, a dirty shutdown is done by holding the power switch until all power is cut. PC's in a dirty power down state, can fail to WOL, so be sure to check that.... cheers anyweb

i dont get your question, can you try to re-word it please ?

try this one

SQL Server 2008 Service Pack 1 (SP1) is now available. You can use these packages to upgrade any SQL Server 2008 edition. Note:We remain committed to our plans to keep service packs contained, focusing on essential updates only, primarily a Roll-up of Cumulative Update 1 to 3, Quick Fix Engineering (QFE) updates, as well as fixes to issues reported through the SQL Server community. While keeping product changes contained, we have made significant investments to ease deployment and management of Service Packs: Slipstream – You are now able to integrate the base installation with service packs (or Hotfixes) and install in a single step. Service Pack Uninstall – You are now able to uninstall only the Service Pack (without removing the whole instance) Report Builder 2.0 Click Once capability For more information about SQL Server 2008 Service Pack 1, please review the Release Notes. download link > http://www.microsoft.com/downloads/details...;displaylang=en

you can pretty much forget about OSD and rebuild everything from scratch with SCCM, in SMS we had to install the OSD feature pack just to install OS's in a managed way, with SCCM, operating system deployment is built in from the word go, the only thing you need to add to SCCM is Microsoft Deployment Toolkit if you plan on customising roles and features in Windows Server 2008 or for extra abilities while creating task sequences. If I was upgrading from SMS to SCCM, i'd rebuild everything from scratch and do it in a lab first, but if you have to upgrade then test it first in a limited way using a lab setup. please post how you decide to go here as I'd like to hear about your decisions in this regard and I have read the replies you got on myitforum also cheers anyweb

great work wmmayms ! keep the reports coming

well spotted, and p.s. that info is already in part 2 of setting up SCCM 2007 right here ;-) cheers anyweb

hmm, ok then something is wrong, did you extend the AD schema for SCCM ?

welcome what type of domain user are you configuring SCCM with ?

Step 2. Import Management Packs In the SCOM Console, click on import management packs, normally you should only import one management pack per every 24 hours to give them time to settle, but in a lab we can be more adventurous. We will now import the Windows Server Operating System Management Pack. Browse to the folder that you installed the Management Pack into and select the individual packs you need, for example, I don't have any Windows 2003 or Windows 2000 servers in this lab so I don't select those packs. Once selected, choose Open and then click on Import After some time you will be able to close the window. We will now import the Active Directory Management Pack. Open the SCOM Console and click on Administration, to the right, click on Import Management Packs. Browse to the Microsoft Active Directory 2000 2003 and 2008 Management Pack for Operations Manager 2007 folder and in the right pane select some packs, as before i'm not using Server 2000 or Server 2003 in this lab however you must select both the Server 2000 and 2003 Discovery Packs otherwise the Server 2008 Monitor Management pack will fail. click on Import when ready click close once they are all imported

The SCOM DVD already has a folder on it called ManagementPacks which contains 42 predefined Management Packs, however the best practise is to get online and download the current version of any given Management Pack. Step 1. Download and Install Management Packs The following website contains Management Packs ready for download. In this exercise we will download the Active Directory Management Pack. Once you have downloaded the Management Pack, double click on the MSI file and choose Run. Accept the Eula and click Next. Leave the installation Path as default (c:) confirm the Installation and click on Install click continue when prompted by UAC and click close when the Installation of the Management Pack is complete. You can now see the Management Pack files listed in Explorer, open the OM2007_MP_AD2008.DOC for details about configuring and installing the Management Pack. In there you'll see that we must import Microsoft.Windows.Server.Library from the Windows Base OS Management Pack before we install the Active Directory Management Pack. So Let's do that. Download the following Windows Server Operating System Management Pack for Operations Manager 2007 Once downloaded, install it exactly as you did above for the Active Directory Management Pack. Read the Guide that comes with this download, and note the following:

Behind the console you'll have the encryption key backup or restore wizard click Next and choose backup the encryption key click on browse and browse your network to a suitable backup location enter a Password for authorising backup or restore Finally when you are done click on Finish. To continue this series, read How can I configure Operations Manager 2007, Part 1. Configure Computers and Devices to Manage.

This guide assumes that you have installed SCOM 2007 SP1 as outlined here in the 4 part guide. In the SCOM console, click on Configure computers and devices to manage when the computer and device management wizard appears click Next for the Auto or Advanced screen Select Automatic computer discovery and click Next On the Administrator Account screen, select Other User account and provide the credentials for an account with administrative permissions on the computers where agents should be installed, the account in the screenshot below is a Domain Admin (da) account just for this purpose. This is sufficient for this Lab but you should consider alternatives in a production environment for security reasons. click Discover. On the Select Objects to Manage screen, select the computers you would like to install agents on and click Next Leave the summary screen as it is and click finish after some time you should see an agent management task status, click close when done. Take me to How can I configure Operations Manager 2007, Part 2. Import Management Packs

This 4 part Step by Step guide will help you to get System Center Operations Manager 2007 SP1 installed and running on Windows Server 2008. The guide covers all the steps needed to get SCOM 2007 SP1 installed and working in your lab environment, there are screenshots and helpful text every step of the way. Install Part 1. Create AD accounts Part 2. Install IIS and required role services Part 3. Install SQL Server 2005 sp3 Part 4. Install Operations Manager 2007 Configure Now that you have Setup Operations Manager 2007, you will need to configure it. Part 1. Configure Computers and Devices to Manage Part 2. Import Management Packs

here's part of your problem from the log please check that your Network Access Account is set properly this is then followed by which repeats itself many times and could be related to the network access account or misconfigured DNS and finally so, check your network access account in client agents, computer client agent and verify dns is working properly using nslookup cheers anyweb

Step 2. Add .NET Framework 3.0 Components and Powershell Install .NET Framework 3.0 Components and Powershell Start up Server Manager and scroll down to Features, click on Add Features. Expand the .NET Framework 3.0 features and select .NET Framework 3.0 scroll down and select Windows Powershell click Next to proceed and at the confirm installation selections screen click on Install click Close when done Continue on to Part 3. Install SQL Server 2005 sp3

Download and install the following 4 hotfixes on your SCOM server and on any Windows 2008 Server that will be monitored by SCOM. Below are the X86 hotfixes: KB951116 KB952664 KB953290 KB951327 Below are the X64 hotfixes: KB951116 KB952664 KB953290 KB951327 Once they are all installed, reboot. Download the System Center Operations Manager DVD from Technet or MSDN. The file I used here for this guide is the Service pack 1 version of SCOM 2007 called en_system_center_operations_manager_2007_with_service_pack_1_x86_dvd_x14-05942.iso, once downloaded, burn to DVD or mount with daemon tools or similar. Note: Microsoft offers a 180 day Evaluation of SCOM 2007 SP1 here. Step 1. Install SCOM 2007 sp1 Login to the SCOM server as a member of the OpsMgrAdmins Security Group. Double click on SetupOM.exe from the OpsMgr 2007 installation media. In the System Center Operations Managager 2007 Setup window, click Install Operations Manager 2007 When the Welcome to the System Center Operations Manager 2007 Setup Wizard screen appears, click Next On the End User License Agreement screen, select the I accept the terms in the license agreement option, and then click Next. Enter your product registration values and key and then click Next. On the Custom Setup screen, verify that all options are set to This component, and all dependant components, will be installed on the local disk drive and change the default installation location to D:\Program Files\System Center Operations Manager 2007\, and then click Next. The installer will now do a Prerequisites check and if you forgot any component such as .NET or Powershell then it will fail, however you may also get a warning if the amount of RAM present is less than 2GB (as in my case, I have 512 on this virtual machine for the lab). You can view the log or click next to continue. Note: If you have failed the Prerequisites check you cannot continue until you resolve the failures. Enter SCOMMGMTGRP as the Management Group name and change the default Administrator by clicking Browse and point to the OpsMgrAdmins Security Group we created in AD click Next to continue Leave the Database Instance and Port settings as they are, click next On the management server Action Account page, accept the default Domain or Local Computer Account option, enter the credentials of the management server Action account (SA-OpsMgrMSAA), and then click Next. Leave the Database and Log file locations as they are, in a production environment you would want to separate the Log and DB files to separate SAN drives, but this is only a lab so it's fine like this, in addition, in production with 10 or so Management Packs you'd want to increase the size of the DB to 5000mb, the default 1000mb is fine for lab. For Management Server Action Account enter the credentials of the management server Action account (OpsMgrMSAA) that we created in Part 1, and then click Next. For the SDK and Config Service Account screen, select the Domain or Local Account option and enter the credentials for the SDK and Config service account (OpsMgrSDK) that we created in Part 1, and then click Next. For web console Authentication configuration leave it as default, For the Customer Experience Improvement Program screen, make your choice and then click Next. and for the Microsoft Update screen, make your choice and then click Next. finally on the Install the Program screen click Install. after a long while, you'll see the completing System Center Operations Manager screen, leave both options checked. the console will open up and you can now start using System Center Operations Manager 2007 SP1. Congratulations !!

Step 2. Install Service Pack 3 for Sql Server 2005 Download SP3. Double click on the SQL Server 2005 SP3 installation file, when the Open File – Security Warning appears, click Run In the User Account Control message box, click Continue, on the Welcome screen, click Next At the License Terms screen, check I accept the agreement and click Next For the Feature Selection screen, click Next On the Authentication screen, click Next On the Error and Usage Report Settings screen, verify that no check-box is checked and click Next, and for the Running Processes screen, click Next On the Ready to Install screen, click Install If you get prompted with a Program Compatibility Assistant, click Run Program, On the Installation Complete screen, click Next On the Additional Information screen, uncheck Launch the User Provisioning Tool for Windows Vista after SP3 Installation Completes and click Finish Reboot the server Continue on to Part 4. Install Operations Manager 2007

Step 1. Add IIS and required role services The Reporting Services functions within System Center Operations Manager require the IIS role and specific IIS role services in order to function, so we will install them now. Log on to the server with an account with Local Administrative permissions. IE: log on as a user that is a member of the OpsMgrAdmins Security Group in AD. Start Server Manager, Click Roles and Add Roles On the Before You Begin page, click Next, On the Select Server Roles page, check Web Server (IIS), in the Add features required for Web Server (IIS)? page that pops up, click Add required features and click Next On the Select Server roles page verify Web Server (IIS) is selected and click Next On the Introduction to IIS page click Next On the Select Role Services page, check the following roles, then click Next Web Server Common HTTP Features Static Content Installed Default Document Installed Directory Browsing Installed HTTP Errors Installed HTTP redirection Installed Application Development ASP.NET, Installed (add the required features when prompted) .NET Extensibility Installed ASP Not Installed CGI Not Installed ISAPI Extensions Installed ISAPI Filters Installed Server Side Includes Not Installed Health And Diagnostics HTTP Logging Not Installed Logging Tools Not Installed Request Monitor Not Installed Tracing Not Installed Custom Logging Not Installed ODBC Logging Not Installed Security Basic Authentication Not Installed Windows Authentication Installed Digest Authentication Not Installed Client Certificate Mapping Authentication Not Installed IIS Client Certificate Mapping Authentication Not Installed URL Authorization Not Installed Request Filtering Installed IP and Domain Restrictions Not Installed Performance Static Content Compression Not Installed Dynamic Content Compression Not Installed Management Tools IIS Management Console Installed IIS Management Scripts and Tools Not Installed Management Service Not Installed IIS 6 Management Compatibility IIS 6 Metabase Compatability Installed IIS 6 WMI Compatability Installed IIS 6 Scripting Tools Installed IIS 6 Management Console Installed FTP Publishing Service FTP Server Not Installed FTP Management Console Not Installed On the Confirm Installation Selections page, click Install On the Installation Results page, click Close Click Start, Run and type Services.msc, click OK Verify that the World Wide Web Publishing Service is started and that the startup mode is set to Automatic, if not, configure it to automatic and start it.

it looks ok but something is obviously wrong, what have you missed ?????? double check everything