Computer Naming



Aaron’s ReviewDuring the testing of the first task sequence intended for use with new computers / bare metal, there are a few items that Aaron noticed. Aaron has identified several opportunities to correct problems, and has made note of the main appearance for the problem and detailed corrective actions he will take to address the issues with the next round of testing.Lessons Learned TOC \o "1-3" \h \z \u Computer Naming PAGEREF _Toc381914232 \h 2Problems Discovered PAGEREF _Toc381914233 \h 2Corrective Actions PAGEREF _Toc381914234 \h 2Software Updates PAGEREF _Toc381914235 \h 4Problems Discovered PAGEREF _Toc381914236 \h 4Corrective Actions PAGEREF _Toc381914237 \h 4No Checks for Pre-Existing Operating System PAGEREF _Toc381914238 \h 5Problems Discovered PAGEREF _Toc381914239 \h 5Corrective Actions PAGEREF _Toc381914240 \h 5Deployed Systems are not localized PAGEREF _Toc381914241 \h 7Problems Discovered PAGEREF _Toc381914242 \h 7Corrective Actions PAGEREF _Toc381914243 \h 7Some Hardware Devices in Systems Non-Functional PAGEREF _Toc381914244 \h 8Problems Discovered PAGEREF _Toc381914245 \h 8Corrective Actions PAGEREF _Toc381914246 \h 8Computer NamingAaron needs new devices deployed on the FourthCoffee enterprise network to conform to certain naming standards. Problems DiscoveredComputers ended with a random Computer name such as MININT-QLIEOAL and have been joined to the domain in Computers Container in FourthCoffee’s Active Directory.Figure 1: FourthCoffee Active Directory Depicting MININT ComputersIf Computers which are not known to the Configuration Manager infrastructure are installed they will end up with a random generated computer name. Figure 2: Randomly Generated Computer NameIf the task sequence is interrupted for any reason in the Windows PE phase, an “Unknown” record for the computer is created and the computer appears in the All Systems collection.Figure 3: Unknown Computer Object In Configuration ManagerCorrective ActionsAaron plans to use an empty variable named OSDComputername to prompt for a Computername. Aaron will set the variable on the All Unknown Computers collection, so that all new computers / bare metal systems that run the task sequence first prompt for a value for the variable. This ensures that all new systems get a computer name that matches the FourthCoffee computer naming standards.457200000Figure 4: Prompting for Variable ValueWhile this article refers to Configuration Manager 2007, Aaron found that the technique is till valie in Configuration Manager 2012. How to use a collection variable to prompt for a computer name during an OS Deployment Task Sequence in System Center Configuration ManagerSoftware UpdatesAll systems deployed by Configuration Manager at FourthCoffee must have the latest software updates installed.Problems DiscoveredEven though Aaron *DID* specify Install all software updates when he created the new computers task sequence, no updates were being installed on new devices.Corrective ActionsAaron started by reviewing Software Updates in Configuration Manager. Aaron must deploy a software updates package containing all anticipated updates to the All Unknown Computers collection. Unknown devices installing an operating system will only see the software updates deployment targeted to the All Unknown Computers collection. If there is no software updates deployment, then the Install Updates task sequence step conducts no action on devices during the task sequence.No Checks for Pre-Existing Operating SystemThe “new computer” task sequence Aaron created could be used on existing Configuration Manager clients. If the task sequence accidently runs on an existing client no user data is captured AND the computer hard drives are formatted, user data loss will occur. This is unacceptable for FourthCoffee. Problems DiscoveredThe new computer / bare metal task sequence does not check to determine if the task sequence is being started from an existing Configuration Manager client. If run from an existing Configuration Manager client, there is likely to be user data present. FourthCoffee needs to be able to preserve user data if it is present on systems where operating system deployment will occur.Corrective ActionsFor a task sequence that will be used ONLY on new computer hardware, where no existing user data is found, a new group can be inserted into the beginning task sequence that will contain all other groups and steps. Place a check on the options of the group to determine if it is running Windows PE before allowing any task sequence steps to execute. This will prevent the task sequence from starting if run from an existing Configuration Manager client.Figure 5: Check to For Bare Metal in Task SequenceIn addition to this check, Aaron will also ensure this “New Computer” task sequence will also be deployed and available to Only media and PXE:Figure 6: Setting Deployment Availability OptionFor those devices which already have an operating system, and user data, Aaron will plan to use Check Readiness and User State Migration Tool. During his research Aaron discovers an article how to migrate user data from Windows XP to Windows 8.1. Deployed Systems are not localizedFourthCoffee has users in several regions around the world, each with their own localization requirements.Problems DiscoveredAfter the first testing with the “New Computer”, none of the new operating systems contain proper localization.Corrective ActionsAt FourthCoffee, localization and group policy work together to shape the end-user experience. Aaron has added the Dynamic Variables task sequence step to the “New Computer” task sequence in order to control in which Active Directory domain Organizational Unit (OU) the computer will be placed, based on its current physical location. This approach and combination of features will allow Aaron to specify the domain OU automatically when a new computer account is added to the FourthCoffee domain. If the task sequence variable OSDDomainOUName contains a value, it is used to add the computer account to the domain. Populating OSDDomainOUName with a value prior to the Apply steps in the task sequence (such as Apply Operating System, Apply Windows Settings, or Apply Network Settings) will allow the variable to be used as Aaron intends. Figure 7: Set Dynamic Variables Using Computer Location to Set Variable ValueAaron discovers something else useful about the Set Dynamic Variables task sequence step as well: it populates some read-only variables which could be useful._SMSTSMakeMicrosoft Corporation_SMSTSModelSurface Pro 2_SMSTSMacAddresses00:15:5D:00:00:00_SMSTSIPAddresses192.168.4.13,fe80::1954:9063:985:db59_SMSTSSerialNumber2746-6653-7669-7221-8220-9580-02_SMSTSAssetTag2746-6653-7669-7221-8220-9580-02_SMSTSUUID9DF445B7-3C25-4848-82B5-2D9019280710Figure SEQ Figure \* ARABIC 8: Read-Only Variables Populated with Set Dynamic Variables StepSome Hardware Devices in Systems Non-FunctionalApply Device Drivers did not install all devices on Aaron’s test clients. Tests using Apply Driver Package instead had a higher success rate. Problems DiscoveredAfter the new computer task sequence completes, some hardware devices attached to the system are non-functional.Figure 9: Device Manager Showing Device Drivers Missing Corrective ActionsUsage of Apply Driver Package instead of Apply Device Drivers and filter them based on Make and Model. These attributes are populated by the Set Dynamic Variables task sequence step Aaron is already using.Other devices such as video adapters will be installed as Applications or Packages.Figure 10: Apply Driver Package in Task SequenceFigure 11: Condition to Satisfy to Apply Driver Package ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download