anyweb

Final configuration Give the site server computer account Admin rights to the site system Note: if you have setup SQL on a server which is NOT the active directory domain controller, then merely add the Computer account as a member of the Local Administrators group on that server as in the screenshot below. However, if you are installing an All In One server (DC with SQL etc...) then do as follows: Start up Active Directory Users and Computers, and verify that Advanced Features are selected under View Select Builtin in the Left pane, highlight Administrators in the right pane and right click, choose properties and click on the Members Tab, click Add. when the Select Users, Contacts, Computers or Groups window appears, choose Object Types when the Object Types window appears, put a checkmark in the Computers option click Advanced, followed by Find Now add the computer account by clicking it's name and Ok. Click Ok again and now you should see the computer account added Check TCPIP properties for listening IP address in SQL Server Configuration Manager Start up the SQL Server Configuration Manager, and expand SQL Server Network Configuration on the left pane, highlight Protocols for <Instancename> and double click on TCPIP in the right pane Click on the IP Addresses tab change the Status from Disabled (default) to Enabled for both the Servers local ip and localhost values (see screenshots) restart the SQL service to make the changes work that's it ! all Done. Side note: To open the firewall for Windows Server 2008 read this post

Part 2. Install it ! Start the SCCM 2007 SP1 DVD and click on Configuration Manager 2007 SP1 under Install review the welcome screen Choose the first option, Install a Configuration Manager site server accept the license... Next we get to choose the type of installation, as we want to see all the options, choose Custom For Site Type, stick with the default (primary site) decide if you want to participate in CEIP Specify your key where to install it enter your Site Settings and Site Code name For the mode type, choose mixed mode (it is easier to setup and we can always migrate to Native mode in the future). specify your client agent settings... enter your Database server details specify your SMS provider settings Note: The SMS Provider can be installed on the site database server computer, site server computer, or another server class computer (during setup at this point). The SMS Provider is used by the Configuration Manager console, Resource Explorer, tools and custom scripts used by Configuration Manager Admins to access site information stored in the site database. specify the management point decide your TCP port settings check for updates create a local folder to store these updates if necessary updates will be downloaded... once done, click ok to review your settings summary and click Next to start the prerequisite check (final) as everything is ok, you can click on Begin Install After a long wait you should see this lets launch the configuration manager after closing and click on Finish to finish the installation. Congratulations, SCCM 2007 SP1 is now installed ! Note: At this point REBOOT your server. Next step > SCCM 2007 SP1 configuration guide - Part 1 The guide covers:- Adding SCCM computer account to SMS groups, setting site boundries and verifying the site name is configured for Active Directory and setting and configuring the site system roles.

Active Directory Schema Extensions This guide was prepared to help you setup SCCM in a Lab environment. Before extending your Active Directory, make sure to have considered any possible implications of doing so, for example if something does go wrong during the procedure then you'll want to have a backup in place. SCCM needs the Active Directory schema to be extended, so to do so we'll need to copy the EXTADSCH.EXE file ffrom the SCCM DVD. This guide assumes you have installed Windows Server 2008 and configured it for Active Directory and DHCP. This guide also assumes you have access to your SCCM 2007 DVD (or ISO). Looking at how to extend the schema is complex. Updating the schema requires you to be in the Schema admin security group, even an Enterprise Administrator is not a Schema admin. As Microsoft say I decided to use the extADSch.exe method and located it on the SCCM 2007 DVD (F:\SMSSETUP\BIN\I386), but before doing so I wanted to make my Enterprise Administrator a member of the Schema Admins Group. Adding the Enterprise Administrator Group account to the Schema Admins Group to do this, start up Active Directory Users and Computers and select the Enterprise Admins group double click the group and select the Member Of Tab click Add and type Schema then press Check Names click OK notice that it (schema admins group) is now listed in the Member of Tab. click ok when done and now we can try running the extadsch.exe tool, we will run it from an elavated command prompt and redirect any output to a file to see if there were any problems during the process. To open an elavated command prompt do as follows:- click on start and right-click on the Command Promtp icon at the top of the start menu, choose Run As Administrator now we can run our code extadsch.exe > c:\output.txt if everything went ok the log file will be pretty emtpy otherwise it may contain errors, in addition you should see another log file in c:\ called ExtADSch.log here is a sample of a successful schema extension:- that's it, you have now extended the Active Directory schema in Windows Server 2008. Now that you have extended the schema you should give the Primary SCCM server (and Management Point) permissions on the System Management container in AD.

In this guide I have used the 180 Evaluation version of Microsoft SQL Server 2008 Enterprise Edition, this was installed on a Windows Server 2008 which had been pre-configured with AD, DHCP, WDS, IIS. This is a LAB environment, and for the purpose of this guide it's irrelevant that AD,DHCP and WDS are running on this server. in production of course you would want to separate server roles. Your results may vary, try this on a lab computer to verify the steps needed and how they work for you. This Post is NOT SCCM specific and is provided as is to help you get up and running in a lab environment. The specific roles installed in this sample install are not in any way customised for an SCCM install. In a Production environment, you should consult Technet to verify best practices for where to install SQL and to separate the DB and LOG files to SAN drives if appropriate. If you are installing SQL for SCCM then install it on the same server that you will install SCCM on.. Insert the DVD or mount the iso (SQLFULL_ENU.iso), once done double click on setup.exe in case it doesn't autorun. If you get a requirements needed message click ok so that it can install them (updated .NET framework and Windows Installer) Microsoft .NET Framework 3.5 SP1 update Accept the license agreement for the .NET update and click install The actual installation seems to take a few minutes.... if it fails it will give you an error log, you can try installing it again or read the installation issues readme. Windows Installer 4.5 Update Next you may be promted to install a hotfix (KB942288), click Ok. if you were prompted to install the hotfix then you'll be asked to Restart, so lets do that... after the restart and now that we've updated those two components run setup.exe again from the SQL 2008 iso (dvd). You should see the following Planning phase click on System Configuration Checker to check our system for any problems that may prevent SQL 2008 from installing/working. In my case i got one warning (telling me that installing SQL server on a domain controller is not recommended) but I choose to ignore that warning. Clicking ok brings you back to the SQL 2008 main menu, here you can see many more options for your SQL server (hardware requirements, security documentation, release notes, upgrade advisor and more). Installation Click on Installation in the left pane, in the new window that appears, choose the first option which is a new SQL server stand-alone installation. setup support rules this is turn will do a quick test for setup support rules, click ok to continue at this point you can use the drop down menu to select a different SQL version (we dont need to) or input your SQL Server product key, click next when done. accept the license terms and click next click install to install setup support files... once again, I was presented with another setup support rules test result this time with two warnings, the domain controller one (safe to ignore) and my windows firewall telling me that the appropriate ports should be opened I clicked next. Feature Selection I chose to Select All and left the path of the install as default. Instance Configuration I left these options as default Disk Space Requirements The disk space requirements gave me a green ok arrow, so I clicked next to continue Server Configuration Note: if you need to change collation, or verify it then click on the Collation Tab. Otherwise, click on Account Name to the right of SQL Server Agent and enter your the administrator/password values click next Database Engine Configuration You can adjust the user settings here depending on your security preferences for the purpose of this guide, we will add the local administrator by clicking on Add Current User, if this or any options confuse you then click on help in the bottom right corner of the installer. For Analysis Services configuration, enter the same value (add current user, assuming you are doing this as local administrator...) for the Reporting Services configuration, I left the default value (native) choose your Error and Usage reporting settings and click next your installation Rules will get a quick check... click next to see 'Ready to install' summary' click install to start the installation... (time for lots of coffee..) After dinner it was completed one more click and then it's all completed. :-) Note: This step is optional for troubleshooting Kerberos authentication issues. The named pipes protocol is not required for Configuration Manager 2007 site database operations and should only be used for troubleshooting kerberos authentication problems. Enable Named Pipes and TCP/IP in your SQL server protocols (by default they are disabled), start up your SQL Server Configuration Manager, expand SQL Server Network Configuration in the left pane, and choose Protocols for MSSQLSERVER (or whatever your SQL server instance is called). Right click on named pipes and set to enable, do the same for TCP/IP, once done you must Restart the SQL server service (click on SQL Server Services in the left pane, and in the right pane right click on SQL Server (MSSQLSERVER), choose restart

The guide requires you to download the WSUS package from here and you must also download the Microsoft Report viewer redistributable. This guide also assumes that you have setup and installed IIS in Windows 2008 and that you have configured and installed SQL 2008 or SQL 2005. Please note: Since this guide was originally written, WSUS SP2 has been added as a role within Server 2008 R2 so if you are using Server 2008 R2 you can install WSUS Sp2 by adding the role. Overview WSUS 3.0 SP1 delivers important customer-requested management, stability, and performance improvements. Some of the features and improvements include: * Support for Windows Server 2008. * Support for SQL Server 2008. * Enhanced bulk approval capability, preserving existing approvals. * Support for separate proxy servers and ports for SSL and non-SSL traffic. * Office Excel report export. WSUS 3.0 SP1 can be installed alone, or as an upgrade of either WSUS 3.0 RTM or WSUS 2.0 SP1. This package installs both the WSUS 3.0 SP1 Server and WSUS 3.0 SP1 Administration Console components, for all Windows Server 2003 SP1 supported languages. Additionally, the WSUS 3.0 SP1 client is included in all supported client platform languages. You must install the server components on a computer running Windows Server 2008 or Windows Server 2003 SP1 or later. You may install the Administration Console on a remote computer running Windows Server 2008, Windows Vista, Windows Server 2003 SP1, or Windows XP SP2. WSUS 3.0 SP1 Server Installation on Windows Small Business Server 2003 If you are installing the WSUS 3.0 SP1 product on Windows Small Business Server 2003, follow the instructions in Installing Windows Server Update Services 3.0 on Windows Small Business Server 2003. There are 4 common methods of deploying WSUS: * Single WSUS server * Multiple independant WSUS servers * Multiple Internally synchronised WSUS servers * Disconnected WSUS servers A Single Wsus server would be suitable for a small or simple network. It will synchronise with Microsoft update and then distribute its updates to your servers/clients. Multiple independant WSUS servers could be setup to synchronise with microsoft Update and configured to for example, update only one specific type of client, eg: XP clients or Vista, then another WSUS server in your organisation could be setup just to update your Server 2008 servers. Multiple Internally synchronised WSUS servers is where you have multiple WSUS servers in your organisation but only one connects to Microsoft Update, this is called the Upstream WSUS server and all other WSUS servers (called the Downstream WSUS servers) synchronise via this WSUS server. The synchronisation methods can be either Autonomous or Replica. Disconnected WSUS servers are not connected to the internet at all. You would typically utilise this setup in an organisation that doesn't have or allow internet access. The Microsoft Updates would have to be pulled down from another internet conencted WSUS server and then burned to cd or dvd and copied to the disconnected WSUS server. Installation Install the Report Viewer first Double-click on the Report viewer exe, choose next to continue at the welcome screen accept the license terms click Install to install once done click finish. Install WSUS Double click on the WSUS exe, choose next at the welcome screen choose the Full Server installation accept the license agreement Select your update source (local or on windowsupdate) now if you havn't installed SQL 2008 yet, then please do so as the next screen will allow us to pick between an internal windows database (first option) or to connect to our MSSQL database (default) second option. Choose use existing database as below in the screenshot it will hopefully successfully connect to your database, click next to continue when prompted what IIS website to use, choose the default option (use the existing IIS website) you'll see a summary click next to continue that's it, all done, click Finish. Note: if you are going to use SCCM to manage patch management, then do NOT run the WSUS configuration wizard below The WSUS configuration wizard automatically starts after the Setup wizard completes. Because Configuration Manager 2007 SP1 manages the WSUS settings, you should exit the configuration wizard after it opens.

If you'd like to test the newest version of SQL Server 2008 then look no further Microsoft® SQL Server® 2008 Enterprise Evaluation: Trial Experience for IT Professionals Download SQL Server 2008 180-day Trial Software. Microsoft SQL Server 2008 is a database platform for large-scale online transaction processing (OLTP), data warehousing, and e-commerce applications; it is also a business intelligence platform for data analysis and reporting solutions. Release notes and readme.

Part 4. Install the IIS 6 Management compatibility Open Server Manager, select Roles, Select Web Server (IIS), select Roles services and scroll down to Management Tools, check if IIS 6 Management Compatibility is installed, if it is not installed, click on Add role Services in the right pane and install it. click next to confirm the install, and then Install. Part 5. Install the BITS Server Extensions Open Server Manager, select Features click on Add Features, and placed a checkmark in the BITS Server Extensions box when the 'add role services required for BITS Server Extensions' query comes up, click on Add required role services click next to proceed you'll get an IIS introduction, click next review the new choices it's made for you and click next confirm the selections it made, and click install finally you should see BITS installation successful Part 6. Add ASP (required for ConfigMgr Reporting Point to function) Open Server Manager, select Roles, Select Web Server (IIS), select Roles services and scroll down to Application Development, verify that ASP is installed, if it isn't, install it. Summary The following Web Server role services should be installed. IIS Role Services Web Server Common HTTP Features Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection Application Development ASP.NET .NET Extensibility ASP ISAPI Extensions ISAPI Filters Health and Diagnostics HTTP logging Logging tools Request Monitor Tracing Security Basic Authentication Windows Authentication URL Authorization Request Filtering IP and Domain Restrictions Performance Static Content Compression Management Tools IIS Management Console IIS Management Scripts and Tools Management Service IIS 6 Management Compatibilty IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console

Part 3. Verify that you have Authorization and Authentication configured In IIS Manager, click on Default Web Site in the left pane, and choose the Authentication icon under IIS. in this example (default install of IIS 7 in Windows Server 2008) we can see the following Authentication types are installed Anonymous Authentication - Enabled ASP.NET Impersonation - Disabled Forms Authentication - Disabled We want to add Basic Authentication and Windows Authentication to proceed further. To do this Click on Server Manager and scroll down to Roles Summary. Click on Web Server (IIS) and scroll down to Role Services. In this example both Basic and Windows Authentication are not installed, so let's install them. click on Add role services in the actions pane to the right. scroll down to security and put a check mark in Basic and Windows Authentication, click next. confirm your selections and click install, once done you'll see a results screen At this point you can close the IIS server manager, restart the World Wide Web Publishing Service service (W3SVC) and go back into the IIS server manager, when you click on Default Web Site now and the Authentication icon, you should see the two new authentication methods added. Right click on Windows Authentication and choose Enable (Note: You can use Basic Authentication with WebDAV, but the WebDAV redirector will only use Basic Authentication with SSL connections, so we will not be using it here, I just installed it so that you were aware of it.) In IIS Manager, click the Default Web Site under the Sites node in the tree, Double-click the Authorization rules icon. NOTE: if (like me) you do not see the Authorization rules icon (feature) then go back into Server Manager, select Roles, Select Web Server (IIS), select Roles services and scroll down to Security, check if URL Authorization is installed, if it is not installed, click on Add role Services in the right pane and install it, then restart the Internet Information Services (IIS) Manager. The icon (feature) should now appear.... When the Authorization feature opens, make sure that an Allow rule is defined that includes the administrator account. IE: the default rule for IIS allowing access to All Users will include the administrator account. you can now test logging into your WebDav site using your administrator account by opening a command prompt and typing this net use * http://localhost/ after a few moments you should see a result like this If you don't see the above, for example if you get a an error like this then install the Desktop Experience Feature using the Add Features Wizard) reboot the server and try again. The reason we need the Desktop Experience feature installed in Server 2008 is because it will install the Webclient service which is required for this. Note: if you now get a new error which states Then you must open up IIS Manager, click on Default Web Site, and go into the WebDav Authoring Rules and add the current user you are attempting to do this as (eg: add user DOMAIN\user). See below screenshot. Tip: for a list of webdav errors and solutions to resolving them see this page so now we have mapped drive Z: to the WebDav site, using the administrator account and using the authorization rules we setup above, we have read/write/source acccess to the directory.

get it from here Microsoft® SQL Server® 2008 Express SQL Server 2008 Express is a free edition of SQL Server that is ideal for learning and building desktop and small server applications, and for redistribution by ISVs. Overview Microsoft SQL Server 2008 Express is a powerful and reliable data management system that delivers a rich set of features, data protection, and performance for embedded application clients, light Web applications, and local data stores. Designed for easy deployment and rapid prototyping, SQL Server 2008 Express is available at no cost, and you are free to redistribute it with applications. It is designed to integrate seamlessly with your other server infrastructure investments. For more information about SQL Server Express, including other versons and downloadable components now available, see Microsoft SQL Server Express. Instructions Note: You must have administrative rights on the computer to install SQL Server 2008 Express. We recommend that you read the Release Notes and Readme before installing SQL Server 2008 Express. Step 1: Download and install Microsoft .Net Framework 3.5 SP1. Step 2: Download and install Windows Installer 4.5. Step 3: Download SQL Server 2008 Express by clicking the appropriate link later on this page. To start the installation immediately, click Run. To install SQL Server Express at a later time, click Save. Note: Note: SQL Server 2008 Express includes both 32-bit and 64-bit versions. SQLEXPR32_x86 is a smaller package that can be used to install SQL Server 2008 Express onto only 32-bit operating systems. SQLEXPR_x86 is the same product but supports installation onto both 32-bit and 64-bit (WoW) operating systems. SQLEXPR_x64 is a native 64-bit SQL Server 2008 Express and supports installation onto only 64-bit operating systems. There is no other difference between these packages.

I downloaded a wmv file about SCCM 2007, and when I clicked on it I was greeted with this I chose the default (check web services for a solution) and it showed me the following web page. and I quote: Yes, it's amusing that Microsoft doesn't understand it's own WMV file format. thinking it was a Firefox issue, I tried the same URL in Internet Explorer http://shell.windows.com/fileassoc/0409/xml/redir.asp?EXT=wmv Oddly I got the same result, apparently Windows own websites don't understand what the WMV file extension is for.... A quick google shows lot's of sites that correctly identify the .wmv extension as a Windows Media Video file. Anyway, back to my problem, by default I can't play a wmv file in Windows Server 2008, so to fix this I do as follows:- Open server manager, click on Add features (found under Features Summary), select Desktop Experience and next and then Install, you'll be informed that the Server will need to be restarted after the installation. after the restart, the Add roles wizard will complete it's actions and you'll be able to watch WMV in all it's glory. Alternatively you could save yourself the pain and install VLC.

From the SCCM 2007 ConfigMgr Console --> Site Database --> Site Management --> right click your site + Properties you should see the version number there (see screenshot) Help --> About System Center Configuration Manager displays the same correct version number. Below are the current versions of SCCM 2007 For RTM, it is 4.00.5931.0000 For SP1, it is 4.00.6221.1000 For SP2, it is 4.00.6487.2000 so based on this, the screenshot above is from a SCCM 2007 SP1 system. Is R2 installed ? If you right click on Site Properties you'll see the version number plus you can identify if R2/R3 are installed - see below What about Beta and Release Candiate versions ? For SP2 beta, it is 4.00.6425.2000 For SP2 RC, it is 4.00.6468.2001 cheers niall

you can do it two ways, either by logging in as Administrator and choose Add roles from the Server manager, then add the Web Server role, or as a script here's the script start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementScriptingTools;IIS-ManagementService;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;IIS-LegacySnapIn;IIS-FTPPublishingService;IIS-FTPServer;IIS-FTPManagement;WAS-WindowsActivationService;WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI

Part 2. Download and install Webdav for IIS 7 Note: If you are using Server 2008 R2 which has Webdav 7.5 then read this post first An important note from Microsoft:- pick your version below Microsoft WebDAV Extension for IIS 7.0 (x64) or Microsoft WebDAV Extension for IIS 7.0 (x86) Accept the license agreement and let it install itself Once we have installed Webdav, we need to Enable WebDAV Publishing Using the IIS Manager. Enabling WebDAV Publishing Using the IIS Manager. Startup IIS Manager and in the Connections pane, expand the Sites node in the tree, then click the Default Web Site, then double-click the WebDAV Authoring Rules icon. Click enable webdav in the Actions pane on the right side Once you've clicked it it will then say 'Disable webdav' so be sure not to click there again, now we need to click the Add Authoring Rule task in the Actions pane and set your options as below That's it, you've now enabled WebDAV authoring in IIS 7. We will return to Webdav later in the guide, if you want to do them now then read Step 1 of this post or just continue with the below as we will get to it later anyway.

here's a working SIF and here's the install.bat file referenced in the SIF to install apps/drivers that can't be installed via the SIF

here's a working SIF file and here are the contents of the install.bat file referred to in the sif

The following Step by Step 3 part guide to Deploying Windows Server 2008 using SCCM 2007 covers all the steps necessary to get you up and running in no time at all, screenshots and helpful text show you how to do IT including preconfiguring roles such as Active Directory (ADDS) and DNS. This 3 part guide is aimed at those of you who can succesfully deploy applications (such as Microsoft Office or Firefox) and Operating Systems (such as Windows Vista SP1 and Windows XP sp3. You'll need to be familiar with Microsoft SMS or SCCM and understand what packages, advertisements and collections mean, the guide will however link you to other guides to bring you every step of the way down the entire path. Part 1. * Add new Operating System Install Package * Import new Task Sequence Part 2. * Create and then Update distribution points for the MDT Server packages * Editing the Task Sequence * Adding Server Roles and Features Part 3. * Create a new collection * Advertise the Task sequence to a collection * Add server to collection * Set the IP address as a variable * The Deployment * Troubleshooting PXE errors The guide above has taken a lot of time to document and I'm quite sure that you will find it helpful (lots of screenshots of every step..) good luck, cheers anyweb

With all Windows PE problems and errors that you may (most likely will..) encounter during SCCM OSD Deployment, you'll want to enable the F8 feature in your Windows PE boot images, which allows you to do some basic testing by giving you access to a CMD prompt within the Windows PE session So how do you enable this troubleshooting feature ? locate your boot images in the Operating System Deployment section of SCCM right-click on your chosen boot image (for example 32 bit) and choose Properties Select the Windows PE tab from the properties, and place a checkmark in Enable command support then click apply Don't forget to re-distribute your boot images to their Distribution Points after making this change, and give them some time for doing so. Once distributed, when you PXE boot your clients and you want to troubleshoot any Windows PE deployment issues, press F8 once Windows PE has loadedand you'll get a command prompt. In addition this will keep Windows PE operational in situations where whatever error you were getting would cause Windows PE to reboot with no warnings thereby giving you a chance to read the logs and perform troubleshooting. SMSTS Log File location If the task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\Logs If the task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %Temp%\SMSTSLOG If the task sequence completes when running in Windows PE: <largest fixed partition>\SMSTSLOG Note: In addition, the logs for SCCM (during the Windows PE phase) are stored in X:\Windows\Temp\SMSTSLog\ and C:\SMSTSLog and C:\_SMSTaskSequence. More often than not, the Log file you need to be reading is the smsts.log file to see what is going wrong in your deployment... After Windows PE is done and Windows installation is complete you can find the logs elsewhere such as C:\Windows\System32\CCM\Logs or C:\Windows\SysWOW64\CCM\Logs for 32bit and 64bit respectively. In those directories you'll find a log file named (for example) smsts-20081125-122856.log, the actual name of the file will change based on the date/time that you do the deployment. I've enabled Command Prompt Support, now what ? Once command prompt support is enabled you've got lots of options for troubleshooting. network testing (ipconfig/ping...) or map a share such as net use h: \\servername\share If the user you are trying to logon with is a DOMAIN user then use this format Enter the user name for 'servername': DOMAIN\domainuser disk testing (diskpart...) read LOGS to look for errors that explain why the deployment is failing... using notepad Troubleshooting Links List of Custom Error Codes for Configuration Manager 2007. Troubleshooting tips on Technet see here Troubleshooting made easy > http://blogs.msdn.co...e-easy-way.aspx Sample Troubleshooting Session The Below is taken from a real troubleshooting session... During the Windows PE phase of a Windows Server 2008 Deployment I got an error In the example above it's complaining about a Validate issue in the Task Sequence deployment of Windows Server 2008, looking at the log file located at X:\Windows\Temp\SMSTSLog\ztivalidate I can see that it's complaining about the speed of the processor (because this is a Virtual Machine) so to fix this problem required editing the Validate section of the Task Sequence and removing the check for CPU speed

You need to have completed Part 1 and Part 2 before starting this part. Create a new collection In ConfigMgr right click on Collections and choose new collection for collection name call it Deploy Windows Server 2008 and fill in the comments for membership, click next and ok to the warning, for advertisements and security click next also click close once done and you should see your new empty collection listed. Advertising the Task Sequence to a collection Under the Computer Management node in SCCM ConfigMgr, right-click the collection we have just made (Deploy Windows Server 2008) and choose advertise task sequence fill in the description Build Task Sequence, ..... the task sequence should then be selected by clicking on Browse, select the Server Task Sequence we made earlier select Make this task sequence available to both media and PXE Alternatively, right click the task sequence itself and choose 'advertise' to get to this same step. Schedule Set your schedule depending on whether you are in a Lab or Production Environment. For a Lab Environment Make the Task Sequence mandatory by clicking on the yellow star and select As soon as possible. Select ignore maintenance windows when runing program and allow system restart, set the program rerun behaviour to always rerun program so that we can rerun the task sequence over and over as we require for testing. For a Production Environment In a Production environment set the advertisement from Mandatory to Optional, this gives us less risk of an accidental deployment but also introduces the possibilty of choice. if you want to remove choice then keep the advertisement mandatory but change the program rerun behaviour to never rerun (see below screenshot). Distribution Points set to Access content directly from a distribution point as we will be wiping the hard disc as our first task in the task sequence Interaction adjust interaction to suit your needs Security and security review the summary and click next to proceed, then verify that all went well in the confirmation window. at this point right clicking on our chosen collection and clicking on the Advertisements tab will list the Task Sequence we just added. Add server to collection Under Operating System Deployment, right click on Computer Association and choose import computer information, select Import Single Computer (if you want to import multiple computers select using a file instead) in the example below i'm just giving the server a name and using it's MAC address click next to the data preview and then for Choose Target Collection, hit browse and select the collection we made above click next until the wizard is complete

You need to have completed Part 1 before starting this part. Create and then Update distribution points for the MDT Server packages Now that we have created the Task Sequence, packages files and folders necessary to support the Server deployment we need to make sure to create and then update distribution points for each MDT Server package, the Configuration Manager Client Installation package has already been pushed out to the distribution points so we don't need to do that again. Expand Microsoft MDT Server Settings files and right click on distribution points, click new distribution points and when the wizard starts click next. Select the standard distribution point only and click next, then close when done. Right click the Distribution point and choose upadte distribution points, answer yes at the confirmation screen Repeat the above (create distribution points and then update them) for Microsoft MDT Server Source Files.

Please note that this guide is designed to get you Deploying Windows Server 2008 with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums. In a production environment please consult Technet for best practise, see below links: Operating System Deployment: Operating System Deployment in Configuration Manager Overview of Operating System Deployment Configuration: System Center Configuration Manager 2007 Best Practices: Configuring Configuration Manager Sites for Best Performance Checklist for Security Best Practices Best Practices for Central and Primary Site Hardware and Software Configuration Best Practices for Operating System Deployment Add new Operating System Install Package We will make an Operating System install package, this package will contain the files necessary to support the installation of the Windows Server 2008. In SCCM ConfigMgr expand the Operating System Deployment node and select Operating System Install Package from the list of available options., right click and choose Add Operating System Install Package point to the UNC path of the root of our Windows Server 2008 DVD (which we copied to a network share earlier) eg: \\WIN-AE2V1IRN067\iso\Server 2008 fill in the details click next and review the summary and then click close now that we've added this package, we again need to distribute it to our distribution point, however we will add it only to the normal distribution point and not the pxe one. Expand the Operating System Install Package node we've just added, right click on Distribution Points and choose New Distribution Points. click next when the wizard appears and select the first of the two dist points, then next again click close when done.

Welcome to Engineering Windows 7 Welcome to our first post on a new blog from Microsoft—the Engineering Windows 7 blog, or E7 for short. E7 is hosted by the two senior engineering managers for the Windows 7 product, Jon DeVaan and Steven Sinofsky. Jon and Steven, along with members of the engineering team will post, comment, and participate in this blog. Beginning with this post together we are going to start looking forward towards the “Windows 7” project. We know there are tons of questions about the specifics of the project and strong desire to know what’s in store for the next major release of Windows. Believe us, we are just as excited to start talking about the release. Over the past 18 months since Windows Vista’s broad availability, the team has been hard at work creating the next Windows product. ... We’re excited about this blog. As active bloggers on Microsoft’s intranet we are both looking forward to turning our attention and blogging energies towards the community outside Microsoft. We know the ins and outs of blogging and expect to have fun, provide great information, and also make a few mistakes. We know we’ll misspeak or what we say will be heard differently than we intended. We’re not worried. All we ask is that we have a dialog based on mutual respect and the shared goal of making a great release of Windows 7. Our intent is to post “regularly”. We’ll watch the comments and we will definitely participate both in comments and potentially in follow-up posts as required. We will make sure that members of the Windows 7 development team represent themselves as such as well. While we want to keep the dialog out in the open, please feel free to use email to steven.sinofsky@microsoft.com should you wish to. In particular, email is a good way to suggest topics we might have a chance to discuss on the blog. With that, we conclude our welcome post and ask you to stay tuned and join us in this dialog about the engineering of Windows 7. Steven and Jon The full article > http://blogs.msdn.com/e7/

The Windows 7 craze is barely over, and yet the internet is already buzzing with the next big thing from Microsoft: a project called Midori. The SD Times claims to have seen internal Microsoft documents detailing what Midori actually is, and they say it's the clean-break from Windows many of us have been waiting for. The SD Times article is heavy on the details, and quite technical, but luckily Ars Technica provides a more accessible summary of what Microsoft has in store for Midori. via osnews.com

what steps did you follow to setup DHCP in ipv6 mode ? if it was a guide then give me a link and i'll check it out do your vista clients have a firewall enabled ?

Part 2. Run the SCCM 2007 SP1 installation wizard. Click Next to continue and choose the default option which is to 'Upgrade...'. accept the license and click next decide if you want to participate in the CEIP let the wizard check for updates.... create a new local directory and then give that path to the wizard for the local updates to be stored... updates are downloaded (89 in my case...) you'll be told the update download is complete, and you'll get an upgrade summary clicking next will run the pre-requisite checker again ! but now you'll see a new button, Begin Install Clicking that will start the actual process (how long winded can it all get ?) and this process can take some time (no kidding...) so go make a cup of coffee... or 10 after what seems like an eternity the process will finish and you have to click next... if you liked this guide and would like to see more Free guides, then please DIGG it.

when you try to upgrade SCCM 2007 to SCCM 2007 SP1 by first running the pre-requisite checker, you may see a warning which states:- If you open the file ConfigMgrPrereq.log and look at the errors within, just before the above statement will be a line which reads something like this:- <08-10-2008 21:04:57> Failed to connect to registry for KB940848 with 203. If you have already applied the hotfix from Microsoft then you might need this workaround. The reason for the pre-requisite test getting confused appears to be that it is looking for a string in the REGISTRY but it doesn't match what it's expecting to find Using RegMon from sysinternals I logged the entire process while doing the pre-requisite checks and sure enough it fails to find some keys in the registry even though we have installed the correct hotfix (KB940848), the checker looks for the following key(s) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848 HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848\DisplayName However they are not found because when we installed the hotfix it placed them at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848-v3 as a workaround I created a new regedit file with the exact same info as the v3 one (I exported that key in regedit). Here's the file, rename by removing .txt and run to add this key to the registry. uninstallkb.reg.txt I then did a search and replace, and replaced -v3 with blank. Running the resulting reg file and then starting the pre-req checker again now finally removes the MMC warning from the list ! cheers anyweb