>Everything you could possibly hope to know about Windows 7 certification - Part 2

6:49 PM


Image representing Microsoft as depicted in Cr...Image via CrunchBase

Windows 7 Activation
KMS (Key Management Service) Vs. MAK (Multiple Key Management)
Key Management Service: (Enterprise Environment)
Centralizes the Activation process in a enterprise environment, by running a Key Management Server which does all the communicating with Microsoft about Windows 7 keys. To run this service you are required to have one of the following Windows Operating Systems: Windows 2008 R2 or higher server edition, Windows Microsoft 7 on a machine within your network, a minimum of 25 clients running Windows 7, and DDNS (Dynamic Domain Name System) running within the domain.  KMS must be repeated every 180 days.
Multiple Activation Key(Home or Small Business Environment)
MAK is used for one-time activation with Microsoft’s hosted activation services. There are two ways to activate computers using MAK. The first method is MAK Independent activation, which requires that each computer independently connect and be activated with Microsoft either over the Internet or by telephone. The second method is MAK Proxy activation. With this method, a computer acting as a MAK proxy gathers activation information from multiple computers on the network, and then sends a centralized activation request on their behalf. MAK Proxy activation is configured using the Volume Activation Management Tool (VAMT).
Windows 7 licensing auditing

WMI (Windows Management Instrumentation)

WMI allows Administrators to write WMI scripts or applications to automate administrative tasks on remote computers within the network. Data gathered during activation is accessible by using WMI console.

SMS (Systems Management Server)sp3,  Microsoft System Center Configuration Manager 2007
Using either SMS 2003 sp3 or, Microsoft System Center Configuration Manager 2007 administrators can monitor the license conditions of their network’s clients.

KMS Management Pack
Can be downloaded from the Microsoft website, and used to monitor the KMS service. Logs from the KMS service can be manually viewed using the management pack.

VAMT (Volume Activation Management Tool)

VAMT monitors the KMS and MAK activations over the network. Can give a MAK activation count for clients on network, as well as tell you condition of the license of all clients using volume activation.

1.    Plan and manage software updates.
Application Updates and Operating System updates
Automatic update (Home or Small Business)
Can be used to schedule updates  on a local system automatically or manually.
Choose one of the 4 download methods
·         Install Updates Automatically(Recommended setting)
·         Download Updates but let me choose whether to install them
·         Check for Update but let me choose whether to download and install them
·         Never Check for Updates(Not Recommended) This setting will be used if you choose to centralize the update process
You can also set up how you receive recommended updates, who can update, and to receive featured updates from this option.

WSUS(Microsoft Windows Server Update Services)(Enterprise)
Allows administrators to deploy the latest updates to clients running the Windows operating system. By using WSUS, administrators can fully manage the distribution of updates that are released through Microsoft Update to computers in their network.
·         Requires Application Server and Web Server (IIS) to be running on system.
·         Make sure port 80 for HTTP protocol and port 443 for HTTPS protocol are open on your firewall.

Administrators can set up Updates for Windows 7, and Software by using either the WSUS Configuration Wizard or the WSUS Administration Console.
Save and download information about your upstream server and proxy server.
Choose the language of the updates.
Select the products for which you want to receive updates.
Choose the classifications of updates.
Specify the synchronization schedule for this server.

Using the Windows Server Update Services Configuration Wizard
To save and download your upstream server and proxy information
1.     On the Connect to Upstream Server page of the configuration wizard, click the Start Connecting button. This both saves and uploads your settings and collects information about available updates.
2.     While the connection is being made, the Stop Connecting button will be available. If there are problems with the connection, click Stop Connecting, fix the problems, and restart the connection.
3.     After the download has completed successfully, click Next.

To choose update languages
1.     The Choose Languages page lets you receive updates from all languages or from a subset of languages. Selecting a subset of languages will save disk space, but it is important to choose all of the languages that will be needed by all the clients of this WSUS server.
If you choose to get updates only for specific languages, select Download updates only in these languages, and select the languages for which you want updates.
2.     Click Next.
To choose update products
1.     The Choose Products page lets you specify the products for which you want updates. Select product categories, such as Windows, or specific products, such as Windows Server 2008. Selecting a product category will cause all the products in that category to be selected.
2.     Click Next.
To choose update classifications
1.    The Choose Classifications page allows you to specify the update classifications you want to obtain. Choose all the classifications or a subset of them.
2.    Click Next
To configure the synchronization schedule
1.     On the Set Sync Schedule page, you choose whether to perform synchronization manually or automatically.
If you choose Synchronize manually, you must start the synchronization process from the WSUS Administration Console.
If you choose Synchronize automatically, the WSUS server will synchronize at set intervals. Set the time of the First synchronization and specify the number of Synchronizations per day that you want this server to perform. For example, if you specify that there should be four synchronizations per day, starting at 3:00 A.M., synchronizations will occur at 3:00 A.M., 9:00 A.M., 3:00 P.M., and 9:00 P.M.
2.     Click Next.
3.     On the Finished page, you can start the WSUS Administration Console by leaving the Launch the Windows Server Update Services Administrations snap-in check box selected, and you can start the first synchronization by leaving the Begin initial synchronization check box selected.
4.     Click Finish.

Using the WSUS Administration Console

To choose products and update classifications
1.     In the Options panel, click Products and Classifications. A dialog box appears with Products and Classifications tabs.
2.     In the Products tab, select the product category or specific products for which you want this server to receive updates, or else select All Products.
3.     In the Classifications tab, select the update classifications you want, or else select All Classifications.
4.     Click OK to save your selections.
To choose update files and languages
1.     In the Options panel, click Update Files and Languages. A dialog box appears with Update Files and Update Languages tabs.
2.     In the Update Files tab, choose whether to Store update files locally on this server or to have all client computers install from Microsoft Update. If you decide to store update files on this server, you also decide whether to download only those updates that are approved or to download express installation files.
3.     In the Update Languages tab, if you are storing update files locally, you choose to Download updates for all languages (the default), or to Download updates only in the specified languages. If this WSUS server has downstream servers, they will receive updates only in the languages specified by the upstream server.
4.     Click OK to save these settings.
To synchronize the WSUS server
1.     In the Options panel, click Synchronization Schedule.
2.     In the Synchronization Schedule tab, you choose whether to perform synchronization manually or automatically.
If you choose Synchronize manually, you will have to start the synchronization process from the WSUS Administration Console.
If you choose Synchronize automatically, the WSUS server will synchronize at set intervals. Set the time of the First synchronization and specify the number of Synchronizations per day that you want this server to perform. For example, if you specify that there should be four synchronizations per day, starting at 3:00 A.M., synchronizations will occur at 3:00 A.M., 9:00 A.M., 3:00 P.M., and 9:00 P.M.
3.     Click OK to save your selections.
4.     In the navigation pane of the WSUS Administration Console, select Synchronizations.
5.     Right-click or move to the Actions pane on the right side, and then click Synchronize Now.
If you do not see the Actions pane on the right side of the console, on the console toolbar click View, click Customize, and ensure that the Action pane check box is selected.
6.     After the synchronization is complete, in the left panel, click Updates to view the list of updates.

To set up the client to receive the updates or service packs in an environment that uses Active Directory, you can use an existing domain–based Group Policy object (GPO) or create a new GPO. In an environment without Active Directory, use the Local GPO. You will need to configure Automatic Updates and then point the client computers to the WSUS server.

To approve and deploy an update

1.     On the WSUS Administration Console, click Updates. An update status summary is displayed for All UpdatesCritical UpdatesSecurity Updates, and WSUS Updates.
2.     In the All Updates section, click Updates needed by computers.

3.     On the list of updates, select the updates that you want to approve for installation on your test computer group. Information about a selected update is available in the bottom pane of the Updates panel. To select multiple contiguous updates, hold down the SHIFT key while clicking updates; to select multiple noncontiguous updates, press down the CTRL key while clicking updates.
4.     Right-click the selection and click Approve.
5.     In the Approve Updates dialog box, select your test group, and then click the down arrow.
6.     Click Approved for Install and then click OK.
7.     The Approval Progress window appears which shows progress of the tasks that affect update approval. When approval is completed, click Close.
After 24 hours, you can use the WSUS Reports feature to determine whether the updates were deployed to the test group computers.
To check the status of an update

1.     In the navigation pane of the WSUS Administration Console, click Reports.
2.     On the Reports page, click the Update Status Summary report. The Updates Report window appears.
3.     If you want to filter the list of updates, select the criteria that you want to use, for example, Include updates in these classifications, and then click Run Report on the window's toolbar.
4.     You will see the Updates Report pane. You can check the status of individual updates by selecting the update in the left section of the pane. The last section of the report pane shows the status summary of the update.
5.     You can save or print this report by clicking the applicable icon on the toolbar.
6.     After you test the updates, you can approve the updates for installation on the applicable computer groups in your organization.

3.    Plan and manage a physical hardware and virtualization strategy
Tradeoffs of Physical vs. VDI environment
VDI (Virtual Desktop Infrastructure) is a Domain network designed to give system administrators and end-users the best of both worlds: the ability to host and centrally manage desktop virtual machines in the data center while giving end users a full PC desktop experience
Microsoft VDI solution comprises of following Technologies
 Windows Server 2008 with Hyper-V – Used to enable administrators to virtualize their desktop infrastructure.
 System Center Virtual Machine Manager 2008 – Used for deployment, provisioning, and management of virtualized desktops.
 Windows Server 2008 Terminal Services - virtualizes the presentation of entire desktops or specific applications in a virtualized desktop.
 Microsoft Application Virtualization (App-V) - is part of the Microsoft Desktop Optimization Pack and delivers desktop applications that are never installed, and are dynamically delivered on demand.
 Windows Vista Enterprise Centralized Desktop - is a unique licensing option of Windows 7 for VDI

Advantages of VDI
·         Reduced cost in purchasing desktop computers, as thin clients often last two to three times longer than a desktop computer
·         Centralized Client OS Management
·         Reduction in electricity costs, as thin client computers use only a fraction of amount of energy that is used by a desktop computer. 
·         Improved Data Security
·         Secure Remote Access, as most connection brokers offer an SSL VPN Component and Web Portal
·         Fewer Application Compatibility Problems than with Terminal Server and Citrix, as users have their own, single user OS.
·         Instant provisioning of new desktops
·         Near-zero downtime in the event of hardware failures
·         Significant reduction in the cost of new application deployment
·         Robust desktop image management capabilities
·         Normal 2-3 year PC refresh cycle extended to 5–6 years or more
·         Existing desktop-like performance including multiple monitors, bi-directional audio/video, streaming video, USB support etc.
·         Ability to access the users' enterprise desktop environment from any PC, (including the employee's home PC)
·         Desktop computing power on demand
·         Multiple desktops on demand
·         Self provisioning of desktops (controlled by policies)
·         Zero downtime in the event of client failure

Disadvantages of VDI
·         Many items that are problematic in Terminal Server and Citrix environments exist in VDI
1.     Printing often requires a 3rd party add-on
2.     PDA Sync not supported
3.     Scanning is not natively supported
4.     Bi-Directional Audio is not natively supported
5.     Display protocols not suitable for Graphics Design
6.     Requires low-latency connection between the client and virtual infrastructure
·         Requires Enterprise Class Server Hardware and Storage Area Network
·         For VMs permanently assigned to specific users, these machines need to be patched just like a physical client computer.
Requirements for Windows 7 VDI Server (To run Windows Server 2008 with Hype
r-V service) Remember the MS7 Hard disk requirement of
16 GB available hard disk space (32-bit) or 20 GB (64-bit) for the client
·         1 host for VDI Core
·         At least one 2.0GHz x86 CPU
·         At least 4GB RAM
·         At least 32GB disk space

VHD: (Virtual Hard Disk) is a file formatted to be structurally identical to a physical Hard Disk Drive.(Image, Clone)

Native VHD Boot: the ability of a physical computer to mount and boot from an operating system contained within a VHD. Windows 7 supports this ability, both with and without a host operating system to be present.

--- These notes for Windows 7 certification are provided by Chris Smoot.

Christopher L. Smoot
MCTS LOGOPhotobucket

Transcript ID: 864473
Access code: 12345678

Related articles by Zemanta
Reblog this post [with Zemanta]

You Might Also Like