Jump to content

anyweb

Member
  • Posts

    109
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Sweden

Everything posted by anyweb

  1. so after you made the change you could see your image \?
  2. hi all, Most of you are deploying Windows 7 or Windows Server 2008 in an automated fashion, some of you will use or are using SCCM 2007. I've put together a list of some of the step by step System Center Configuration Manager guides i've created to help those of you who are starting with SCCM and for those of you using SCCM in a lab environment, hopefully this will make it easier for you to find the area that interests you. The main areas are * Setup SCCM * Updating SCCM * Deploying Windows Updates using SCCM * Deploying Applications * Deploying OS * Capturing OS * Task Sequences * Migrating Data using USMT * Asset Intelligence * Troubleshooting and Other I hope that these guides help you to get your Lab up and running in record time and prepare yourself for Production. If you would like to contact me directly about this then reply to this topic or send me a pm, I'm happy to help. cheers Niall. Setup SCCM Installing SCCM Installing SCCM 2007 in Windows 2008 SCCM 2007 SP1 configuration guide - Part 1 covers: setting site boundaries and verifying the site name is configured for Active Directory and setting and configuring the site system roles. SCCM 2007 SP1 configuration guide - Part 2 covers: Configuring the Distribution Point (DP) and the Management Point (MP), adding Authoring rules in WebDav and changing WebDav settings, making sure the System Management container in Active Directory has the correct permissions for SCCM, checking and fixing errors in SCCM System Status. SCCM 2007 SP1 configuration guide - Part 3 covers:Configuring the Client Agents, setting up client installation methods and configuring discovery methods. What Version of SCCM is installed ? Which version is Installed ? how can I backup my SCCM server backup is a good idea Updating SCCM How can I update/upgrade SCCM Sp1 to Sp2 Updating to SP2 Upgrading ConfigMgr Client after SP2 upgrade How can I upgrade the configMgr client after upgrading to SP2 ? Deploying Windows Updates using SCCM Configuring Software Update point within SCCM Configuring Software Update Point within SCCM Configuring another server to run WSUS for SCCM Setting up a Software Update Point on a Remote Server Managing monthly updates in SCCM On the Second Tuesday of every Month Deploying Service Packs using SCCM How can I deploy service packs using the software update point Using Update Lists when deploying Monthly Updates Part 1. Creating the Update List and Deployment Management Task Using Update Lists when deploying Monthly Updates Part 2. Target the Deployment Management Task and Verify Using Update Lists when deploying Monthly Updates Part 3. Using reports to report on Compliance Updates are not being installed automatically - Windows Update Icon The Windows Update icon appears even though SCCM is managing updates Deploying Applications Using SCCM 2007 SP1 to deploy an application Deploying Firefox Deploy software through AD Groups linked to Collections in SCCM, AD Group for deployments everyone needs software eventually How can I install Multiple Applications using a Task Sequence Installing apps via a TS and deciding what order they are installed How can I install multiple applications based on Active Directory Security Group membership in a Task Sequence Dynamic application Installation how can I target applications (and drivers) to specific hardware? target hardware How can I set the permissions for Drivers Packages in SCCM ? Shares and NTFS Deploying OS Adding the PXE Service Point role (PSP) in SCCM Adding the PXE role Operating System Deployment support in SCCM 2007 SP2 what is supported ? Using SCCM 2007 SP1 to deploy Vista SP1 Deploying Vista (6 Parts) Using SCCM 2007 SP1 to deploy XP SP3 Deploying XP (2 parts) Deploy XP SP3 using Task Sequence Media (CD/DVD/USB) Custom Install DVD Using SCCM 2007 SP1 to deploy Windows Server 2008 Deploying Server (3 parts) Using SCCM 2007 Sp2 to deploy Windows 7 Deploy 7 (4 parts) Customising Windows 7 deployments - part 1. Changing the keyboard layout using unattend.xml Customising Windows 7 deployments - part 2. Specifying an Organisational Unit (OU) using the MachineObjectOU variable Setting computername during deployment Using the OSDComputerName variable How can I create a boot image with HTA support using MDT Part 1. Create MDT boot image Set the Screen Resolution during OSD Using SETRES to set screen resolution Capturing OS How can I capture Windows 7 Capturing Windows 7 using a custom task sequence Task Sequences How can I see a report of a Task Sequences Progress Generate a Report of a Task Sequences Progress using Multiple Task Sequences via PXE, PXE boot to a task sequence menu choice is sometimes a good thing How can I password Protect a Task Sequence ? Password Protecting a Task Sequence Migrating Data using USMT how can I use USMT 3.0.1 in SCCM migrate today restore tomorrow how can I view the USMT recovery key user state recovery information How can I use Offline Mode in Windows PE using USMT 4 Using a scanstate (using offlinewindir in winpe ) Task Sequence in SCCM 2007 SP2 Some Sample XP to Windows 7 task sequences showing Hardlinking hardlinking and SMP Migrate XP to Windows 7 using Offline mode in Windows PE screenshots describing the process Asset Intelligence Part 1 - - Enabling Asset Intelligence and selecting Reporting Classes Part 2 - Add the role and enable the online connector Troubleshooting and other Troubleshooting PXE and PE problems Troubleshooting with the help of SMSTS.LOG and F8 Understanding SCCM Logs where are they, and what are they for how can I Import Computers Using a file in SCCM 2007 ? importing computers How can I make a collection for all Windows Vista Systems All Windows Vista Systems How to set a password on PXE boot Setting a password to avoid accidental Operating System Deployment How can I use variables to join domain, set keyboard, regional options Using collection variables to set options Add Trace32.exe to your boot.wim making troubleshooting that bit easier workaround for AbortPxe.com how to get rid of abortpxe.com
  3. For those of you interested in deploying Operating Systems using System Center Configuration Manager 2007, here's a 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
  4. sorry for the delay in replying, i've been busy. i'll try and answer some of your questions, as to your questions: 1. i'd say yes, pretty much, but you'll have to test/verify this, Microsoft offer a VHD of the SCCM 2007 r2 release, test it, it's free to test, but in reality you\ll want to setup a real lab and test it in steps (sccm is huge) 2. wake on lan yes, hibernate ? don't know, but if you can script something then yes via software distribution (packages) a. no idea, b yes 3. no, but you can re-image via pxe, slower but can achieve same thing, almost... 4. ask your Microsoft rep 5. as above 6. yes, absolutely 7. there isn't a feature to broadcast messages per se, but you can advertise a package containing anything you want, to any computers that you define in a collection b. as above, expect linux/mac pcs have to be managed with the addition of a plugin for SCCM via Quest
  5. in my guides, i've had the roles all together but that's just for a lab environment, in production you can separate the roles, see this post for some info about that, I'd suggest you start reading Technet to get an idea of how your subnets can work with SCCM, http://technet.microsoft.com/en-us/library/bb680397.aspx cheers anyweb
  6. stick it here http://www.windows-noob.com/forums/index.php?showtopic=580 Startup Windows SIM and add the Microsoft-Windows-Setup\UserData\ProductKey to the WindowsPE configuration pass. Input your key including all the dashs eg: Y34HR-1GHTU-W15HU-D4MND-L4M3R set the WillShowUI value to Never click on Validate to check your answer file.
  7. thanks for that, and here's a step by step guide to setting up a KMS server for anyone thats interested http://www.windows-noob.com/forums/index.php?showtopic=649 cheers anyweb
  8. very odd ! are they plugged in when installing ? what hardware are they ? how are you installing ?
  9. hi again, more guides added how can I deploy XP SP3 using SCCM 2007 sp1 - part 1 how can I deploy XP SP3 using SCCM 2007 sp1 - part 2 how can I target applications to specific hardware how can I Import Computers Using a file in SCCM 2007 ? and...coming soon, Deploy 7 with SCCM
  10. hi, are you using Windows SIM to make/edit your unattend.xml file ? if so you can do the following with it how can I join a Domain using Windows SIM how can I configure the hard disc using Windows SIM how can I install drivers using windows SIM how can I change computername using Windows SIM how can I add the product key using Windows SIM how can I edit the EULA, FullName and Organization settings using Windows SIM how can I decide which version of Windows get's installed using Windows SIM EDIT it seems you have completely changed your post while i was replying below is your original post... can't you just raise a new post ??? cheers anyweb
  11. product key issues with XP are usually related to the KEY type and media type, ie: a VLK key will only work with VLK *volume license key* media, and a retail key with retail media, same goes for OEM or MSDN media so what type of key are you using (is it one from the side of the pc, if it is it's OEM) and what type of CD did you use for the xp image ?
  12. is your goal to free up space on the DVD for some other stuff or what ?
  13. maybe you could delete the other CLG files on the dvd read more about them here cheers anyweb
  14. hi again i've now added the following guides for you how can I troubleshoot Windows PE booting in SCCM and how to deploy Windows Server 2008 using SCCM 2007 SP1 (3 parts). how can I deploy Windows Server 2008 using SCCM 2007 sp1 - part 1. how can I deploy Windows Server 2008 using SCCM 2007 sp1 - part 2. how can I deploy Windows Server 2008 using SCCM 2007 sp1 - part 3. are any of you using this technology ? any problems ? comments and suggestions welcome cheers anyweb
  15. copy the install.wim file from your microsoft vista DVD to your local hard drive first, then mount that file, it should work fine.
  16. greetings again, i've been updating some more and have now added the following parts (more to come) how can I deploy Windows Vista SP1 using SCCM 2007 SP1, Part 1. This covers the following:- Configuring MDT, PXE and SCCM to get them prepared for Vista Deployment via PXE boot.. Creating a New Collection in SCCM 2007 Creating a Package From Definition to deploy the SCCM 2007 client Create and Update Distribution Points how can I deploy Windows Vista SP1 using SCCM 2007 SP1, part 2. This covers the following:- Adding 32 bit and 64 bit boot.wim files Customise the background Logo Create new Distribution Points and Update them for the boot.wim files how can I deploy Windows Vista SP1 using SCCM 2007 SP1, part 3. This covers the following:- Add New operating system image Create Distribution Point for the Image Add new Operating System Install Package Drivers and Driver packages how can I deploy Windows Vista SP1 using SCCM 2007 SP1, part 4. This covers the following:- Create new Task Sequence Assigning the Task Sequence to a collection how can I deploy Windows Vista SP1 using SCCM 2007 SP1, part 5. This covers the following:- Importing a MDT Task Sequence MDT Package sysprep Package Add Build and Capture Computer PXE boot the client computer now to test the OSD build. how can I deploy Windows Vista SP1 using SCCM 2007 SP1, part 6. This covers the following:- Add captured image to SCCM Create a collection Advertise the Deployment Task Sequence Create Computer Association and that's it ! if you followed all the above you'll be able to deploy Windows Vista SP1 using SCCM 2007 sp1 ! well done !
  17. i've seen a similar problem to the above screenshot when using the BOOT.WIM from the Dell or OEM DVD, if you use BOOT.WIM from an MSDN dvd you should not see the problem.... cheers anyweb ;-)
  18. hi again I've now added the next stage which is how can I deploy an application in SCCM 2007 SP1 this 4 step guide covers: Creating a package Creating a program Advertising the package Distributing the advertisement cheers anyweb
  19. taken from microsoft's technet http://technet.microsoft.com/en-us/library/cc721940.aspx Limitations of Sysprep Sysprep has the following limitations: * You must use only the version of Sysprep that is installed with the Windows image that you intend to configure. Sysprep is installed with every version of Windows and must always be run from the %WINDIR%\system32\sysprep directory. * Sysprep must not be used on upgrade installation types. Run Sysprep only on clean installations. * If you plan to use the imagex /apply command to apply a Windows image to a computer, the partition layout on the reference and destination computers must be identical. For example, if you capture a customized Windows image on drive D, you must always deploy that image onto drive D of the destination computer. The following list describes the partition settings that must be identical across the reference and destination computers when you use the imagex /apply command. o The partition number where Windows Vista is installed must match. o The partition type (primary, extended, or logical) must match. o If the partition is set to active on the reference computer, the destination computer must also be set to active. o If you have another active partition for Bootmgr and BCD stores on the reference system, you must also capture this partition and apply it to the same partition on the destination computer. This limitation applies only to the imagex /apply command. If you run Setup and reinstall Windows, you can change the drive letters where Windows is installed. noteNote In some cases, customized applications that are installed before the Windows image is recaptured might require a consistent drive letter. Some applications store paths that include the drive letter of the system. Uninstallation, servicing, and repair scenarios might not function appropriately if the drive letter of the system does not match the drive letter specified in the application. Deploying customized Windows images to different drive letters is not supported. The recommended practice is, if you are installing customized applications, to deploy your Windows image to the same drive letter. * When you copy Windows images between computers, the reference and destination computers do not need to have compatible hardware abstraction layers (HALs). The /detecthal option in the Boot Configuration Data (BCD) will enable a system that has already run Sysprep to install the correct HAL. * The Plug and Play devices on the reference and destination computers, such as modems, sound cards, network adapters, and video cards, do not have to be from the same manufacturer. However, the drivers for these devices must be included in the installation. * You cannot automate the running of Sysprep by using a RunSynchronous command in auditUser configuration pass. You can automate the running of Sysprep only by using a FirstLogonCommand in the oobeSystem pass. * The clock for activation begins its countdown the first time Windows starts. You can use Sysprep for a maximum of three times to reset the clock for Windows Product Activation. After the third time you run Sysprep, the clock can no longer be reset. * ImageX, third-party disk-imaging software, or disk-duplicating hardware devices are required for image-based Setup. These products create binary images of a computer's hard disk and either duplicates the image to another hard disk or stores the image in a file on a separate disk. * Sysprep runs only if the computer is a member of a workgroup, not a domain. If the computer is joined to a domain, Sysprep removes the computer from the domain. * If you run Sysprep on an NTFS file system partition that contains encrypted files or folders, the data in those folders becomes completely unreadable and unrecoverable. * Sysprep converts the %COMPUTERNAME% environment variable to uppercase characters. However, the actual name of the computer does not change. * Running Sysprep will cause Windows Welcome to prompt you for a product key. You can use an answer file with Sysprep to prevent Windows Welcome from prompting you for a product key. If you specify a valid product key in the ProductKey setting of the Microsoft-Windows-Shell-Setup component during the specialize pass, then Windows Welcome will not prompt you for a product key.
  20. I've also done a guide for setting up WDS in Windows Server 2008, it includes screenshots of the steps required cheers anyweb
  21. hi all, i've been busy setting up SCCM 2007 SP1 in Windows 2008 and now that i've got it installed and working i thought i'd share with you how that was done, it wasn't exactly straightforward so i've documented all the steps I took from installation right through to configuration. This guide assumes that you have first setup Windows Server 2008 and configured it for Active Directory, with DHCP (you only need steps 1 and 2 of this guide), installed and configured IIS (for SCCM) and installed SQL Server 2005 and WSUS. Once you have completed the requirements listed above, you have to install SCCM and that will involve fixing any prerequisite checks and proceeding with the installation itself. Next you have to go through a fairly lengthy configuration process for SCCM, I've broken that down into three parts below:- Part 1 > SCCM 2007 SP1 configuration guide 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. Part 2 > SCCM 2007 SP1 configuration guide The guide covers:- Configuring the Distribution Point (DP) and the Management Point (MP), adding Authoring rules in WebDav and changing WebDav settings, making sure the System Management container in Active Directory has the correct permissions for SCCM, checking and fixing errors in SCCM System Status. Part 3 > SCCM 2007 SP1 configuration guide The guide covers:- Configuring the Client Agents, setting up client installation methods and configuring discovery methods. I hope that some of you find the quide useful, if I get time I will update the guide and include how to deploy an application in SCCM 2007 plus using the OSD feature in SCCM to deploy Windows Vista SP1 using Zero Touch. cheers anyweb
  22. MSFN users please note that the FULL guide including screenshots and Part 2 is here This guide was done on a Windows 2003 Server (sp2) running SCCM 2007 which in turn was upgraded from SMS 2003. As a result, your results may vary, if they do, post them here. Part 1. Run the Pre-requisite checks and fix the warnings/errors reported. First of all download the Service Pack 1 update and then run the EXE file which will unzip it to a folder of your choice (I chose to call the folder sccm2007sp1) Once unzipped you can burn that to a DVD or run the splash.hta file contained in C:\sccm2007sp1\SCConfigMgr07_UPD_EN Once it starts you can run the prerequisite checker to see what you need to fix before continuing... you will be presented with a prerequisite check I left everything as it was and clicked on OK once done you'll get a list of errors that need to be resolved such as below, double click on any one to see what the recommended action is and then action each one My first error told me that I needed to do as follows: as this was a hotfix i was pleasantly surprised to see that Microsoft now allow you to download the hotfix semi-directly, you have to enter your email address twice and input a number displayed on screen, you then get an email with the hotfix download details... So I downloaded the first one and extracted it with the password supplied in the email. While the hotfix installed I clicked OK on the prerequisite checker for SCCM 2007 sp1. Once the hotfix was done installing, it wanted a reboot, so I rebooted. And then I ran the SCCM 2007 SP1 prerequisite checker again by starting at the beginning and running splash.hta... This time however I was down to only 3 warnings Next up I had to do the following:- That brought up a page with 3 download links (xp/windows server and so on).... confusing, inconsistent ? yep.. but I got the following file WindowsServer2003-KB936059-x86-ENU.exe I must have been lucky because when I ran the SCCM sp1 prerequisite checker again, I was only shown 2 warnings (below) Next up was my MMC update Once installed, I ran the SCCM 2007 SP1 pre requisite checker again, it told me i still needed this fix, so I decided to reboot (the hotfix didn't request it), the reboot didn't help it still listed it as a warning... so I viewed the ConfigMgrPrereq.log file (stored in the root of C:\) and it had a line that read Failed to connect to registry for KB940848 with 203 that lead me to this post Using regmon from Sysinternals I found the missing key and made a reg file of it, if you want it make sure you've applied the correct hotfix first then:- As a workaround I've produced the following hack. FQDN Warning. As my SCCM 2007 site is mixed mode I chose to resolve this warning by doing as follows:- To fix the FQDN error try the following: 1. Start SCCM Console 2. Click Site Database 3. Click Site Management 4. Click on Site 5. Click Site Settings 6. Go to Site Systems 7. Click on SCCM Server (where State Migration Point is located) 8. Right click on “Configmgr Site System” 9. Click on Properties 10. In the "Specify a fully qualified domain name (FQDN) for this site system on the intranet” change the Intranet FQDN to something like my example here it was WINDOWS-DOBMTWV I changed it to windows-noob.sccm2007.local and clicked apply, after waiting a few minutes for SCCM 2007 to udpate itself I ran the pre-req checker again and finally, success !
  23. what media are you using for the installation ? OEM or RETAIL or MSDN or ?


×
×
  • Create New...