Windows 7 Editions Comparsion

Availability

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Retail packaging			Yes	Yes	Ult. only
Can purchase electronically			Yes	Yes	Ult. only
Pricing: Full version			$199.99	$299.99	$319.99 (Ult)
Pricing: Upgrade version			$119.99	$199.99	$219.99 (Ult.)
Bundled with new PCs in major markets		Yes	Yes	Yes	Ult. only
Windows Anytime Upgrade (WAU)	Yes	Yes	Yes	Yes
WAU pricing/To Home Premium	$79.99	$79.99
WAU pricing/To Professional		$114.99	$89.99
WAU pricing/To Ultimate	$164.99	$164.99	$139.99	$129.99
Virtualization rights (Can be installed in a virtual environment)			Yes	Yes	Yes

 

User interface features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Windows Basic UI	Yes	Yes	Yes	Yes	Yes
Windows Standard UI	Yes		Yes	Yes	Yes
Windows Aero UI ("Glass")			Yes	Yes	Yes
Aero Peek			Yes	Yes	Yes
Aero Snaps	Yes	Yes	Yes	Yes	Yes
Aero Shake			Yes	Yes	Yes
Aero Background			Yes	Yes	Yes
Libraries	Yes	Yes	Yes	Yes	Yes
Windows Flip	Yes	Yes	Yes	Yes	Yes
Windows Flip 3D			Yes	Yes	Yes
Live Taskbar Previews	Yes		Yes	Yes	Yes
Live Preview (Explorer)			Yes	Yes	Yes
Jump Lists	Yes	Yes	Yes	Yes	Yes
Windows Search	Yes	Yes	Yes	Yes	Yes

 

 

Security features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
More granular UAC	Yes	Yes	Yes	Yes	Yes
Action Center	Yes	Yes	Yes	Yes	Yes
Windows Defender	Yes	Yes	Yes	Yes	Yes
Windows Firewall	Yes	Yes	Yes	Yes	Yes
IE 8 Protected Mode and DEP support	Yes	Yes	Yes	Yes	Yes
Windows Update (can access Microsoft Update)	Yes	Yes	Yes	Yes	Yes
Fast User Switching	Yes		Yes	Yes	Yes
Parental Controls	Yes	Yes	Yes	Yes	Yes

 

Performance features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Windows ReadyDrive	Yes	Yes	Yes	Yes	Yes
Windows ReadyBoost	Yes	Yes	Yes	Yes	Yes
SuperFetch	Yes	Yes	Yes	Yes	Yes
64-bit processor support	No	No	Yes	Yes	Yes
Physical processor support	1	1	1	2	2
Processor core support	Unlimited	Unlimited	Unlimited	Unlimited	Unlimited
Max RAM (32-bit)	4 GB	4 GB	4 GB	4 GB	4 GB
Max RAM (64-bit)	n/a	n/a	16 GB	192 GB	192 GB

 

Reliability features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Windows Backup	Yes	Yes	Yes	Yes	Yes
System image	Yes	Yes	Yes	Yes	Yes
Problem Steps Recorder	Yes	Yes	Yes	Yes	Yes
Backup to network				Yes	Yes
Encrypting File System (EFS)				Yes	Yes
BitLocker					Yes
BitLocker To Go					Yes
Automatic hard disk defragmentation	Yes	Yes	Yes	Yes	Yes
Previous Versions	Yes	Yes	Yes	Yes	Yes
Create and attach (mount) VHD	Yes	Yes	Yes	Yes	Yes

 

Bundled applications

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Internet Explorer 8	Yes	Yes	Yes	Yes	Yes
Windows Gadgets and Gallery	Yes	Yes	Yes	Yes	Yes
Games Explorer with basic games (FreeCell, Hearts, Minesweeper, Purble Palace, Solitaire, Spider Solitaire)	Yes	Yes	Yes	Yes	Yes
Premium games (Internet Backgammon, Internet Checkers, Internet Spades, Mahjong Titans)			Yes	Yes	Yes
Calculator	Yes	Yes	Yes	Yes	Yes
Paint	Yes	Yes	Yes	Yes	Yes
Snipping Tool			Yes	Yes	Yes
Sticky Notes			Yes	Yes	Yes
Windows Journal			Yes	Yes	Yes
Windows Fax and Scan	Yes	Yes	Yes	Yes	Yes
Windows PowerShell and ISE	Yes	Yes	Yes	Yes	Yes
WordPad	Yes	Yes	Yes	Yes	Yes
XPS Viewer	Yes	Yes	Yes	Yes	Yes

 

Digital media and devices

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Windows Photo Viewer	Yes	Yes	Yes	Yes	Yes
Basic photo slide shows	Yes	Yes	Yes	Yes	Yes
Windows Media Player 12 with Play To	Yes	Yes	Yes	Yes	Yes
Windows Media Player Remote Media Experience			Yes	Yes	Yes
MPEG-2 decoding			Yes	Yes	Yes
Dolby Digital compatibility			Yes	Yes	Yes
AAC and H.264 decoding	Yes	Yes	Yes	Yes	Yes
DVD playback			Yes	Yes	Yes
Can install MPEG-2 (DVD playback) add-in	Yes	Yes	n/a	n/a	n/a
Windows Media Center			Yes	Yes	Yes
Number of TV tuners supported			4 of each type (analog, digital, etc.)	4 of each type (analog, digital, etc.)	4 of each type (analog, digital, etc.)
Windows DVD Maker			Yes	Yes	Yes
Device Stage	Yes	Yes	Yes	Yes	Yes
Sync Center	Yes	Yes	Yes	Yes	Yes

 

Networking features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
SMB connections	20	20	20	20	20
Network and Sharing Center	Yes	Yes	Yes	Yes	Yes
HomeGroup sharing	Join only	Join only	Yes	Yes	Yes
Ad-hoc network create and join	Yes	Yes, but accessible only via Start Menu Search	Yes	Yes	Yes
Improved power management	Yes	Yes	Yes	Yes	Yes
Connect to a Projector	Yes	Yes	Yes	Yes	Yes
Remote Desktop	Yes	Yes	Yes	Yes	Yes
Remote Desktop Host				Yes	Yes
IIS Web Server			Yes	Yes	Yes
RSS support	Yes	Yes	Yes	Yes	Yes
Internet Connection Sharing	Yes		Yes	Yes	Yes
Network Bridge	Yes		Yes	Yes	Yes
Offline files				Yes	Yes

 

Mobility features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Windows Mobility Center	Yes (No presentation mode)		Yes (No presentation mode)	Yes	Yes
Windows Sideshow (Auxilliary display)			Yes	Yes	Yes
Sync Center	Yes	Yes	Yes	Yes	Yes
Tablet PC functionality			Yes	Yes	Yes
Multi-Touch support			Yes	Yes	Yes

 

Enterprise features

 

	Home Basic	Starter	Home Premium	Professional	Enterprise & Ultimate
Domain join (Windows Server)				Yes	Yes
XP Mode licensed				Yes	Yes
AppLocker					Yes
Boot from VHD					Yes
BranchCache					Yes
DirectAccess					Yes
Federated Search (Enterprise Search Scopes)					Yes
Multilingual User Interface (MUI) Language Packs					Yes
Location-aware printing				Yes	Yes
Subsystem for UNIX-based Applications					Yes

 

VBscript Configure Clients Internet based Management Point Setting

on error resume next

' Create variables.
Dim newInternetBasedManagementPointFQDN
Dim client

newInternetBasedManagementPointFQDN = "mp.contoso.com"

' Create the client COM object.
Set client = CreateObject ("Microsoft.SMS.Client")

' Set the Internet-Based Management Point FQDN by calling the SetCurrentManagementPoint method.
client.SetInternetManagementPointFQDN newInternetBasedManagementPointFQDN

' Clear variables.
Set client = Nothing
Set internetBasedManagementPointFQDN = Nothing

Wake ON LAN – End to End Configuration at Client Site

Dependencies External to Configuration Manager 2007

Dependency	More Information
Network cards must support the standard Magic Packet format.	All network cards that have the Windows Logo certificate support this Magic Packet format.
Computers must be configured for wake-up packets on the network card and in the computer BIOS.	Refer to your hardware vendor's documentation for information about how to configure this and the wake-up capabilities of the computer.
If you are using Wake On LAN with subnet-directed broadcast, all routers between the site server and target computers must allow IP directed broadcasts, and support IPv4.	Typically, routers are configured to not allow subnet-directed broadcast. Subnet-directed broadcasts are not supported with IPv6.

Configuration Manager 2007 Dependencies

Dependency	More Information
Hardware inventory must be enabled, and completed an inventory schedule.	About Collecting Hardware Inventory How to Configure Hardware Inventory for a Site
The Configuration Manager site must be a primary site.	You can configure child primary sites for Wake On LAN, but not secondary sites. Clients in secondary sites will be sent wake-up packets from their assigned primary site.
Client computers must be running the Configuration Manager 2007 client.	Clients running Systems Management Server (SMS) 2003 do not support Wake On LAN.

It’s biggest challenge that to configure the BIOS settings for all the Desktops when you have different models. I have put my finding here for TOP three Manufactures such as DELL , HP and IBM/Lenovo.

 

The Pre-Requirement at client end includes below two key configurations to be done at each client end.

1) enable Wake-On-Lan in BIOS

2) Configure Power capabilities on Network card Properties from device Manager

 

Okey coming to the first challenge enable Wake-On-Lan in BIOS on three manufactures

1) Dell – dell has DCCM (Dell Client Configuration Utility - Powered by Symantec) and other Management Software it has

2) Lenovo:- I have created a WMI based VBSCRIPT that will Enable WOL BIOS Settings.

' Use at your own risk

'Start Vbscript

'On Error Resume Next

strComputer = "HSCINHYDLT00012"

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\WMI")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM Lenovo_SetBiosSetting")

For Each objItem in colItems
'ObjItem.SetBiosSetting "WakeOnLAN,Disabled"
'ObjItem.SetBiosSetting "WakeOnLAN,Disable"
ObjItem.SetBiosSetting "WakeOnLAN,Enable"
ObjItem.SetBiosSetting "WakeOnLAN,Enabled"
Next

‘end vbscript

3) HP : BiosConfigUtility.EXE a tool from HP

need to show the configuration file to enable the settings

English
S5 Wake on LAN
    *Enable
    Disable

 

Save above fourlines in a text file as CONFIG.TXT.

execute the below COMMAND LINE.

BiosConfigUtility.exe /SetConfig:CONFIG.TXT

and above all can be advertise as software distribution package by creating manufacture based collections.

 

Now the Next key gole is to Configure Power capabilities on Network card Properties from device Manager.

to do this below script can be usefull** test and use with your own risk

‘vbscript start

 

Option Explicit

Dim colNetworkAdapters
Dim objNetworkAdapter

Dim strDevInstanceName
Dim strNetworkAdapterID

'Query for all of the Win32_NetworkAdapters that are wired Ethernet (AdapterTypeId=0 corresponds to Ethernet 802.3)
Set colNetworkAdapters = GetObject("WinMgmts:{impersonationLevel=impersonate}//./root/Cimv2")_
.ExecQuery("SELECT * FROM Win32_NetworkAdapter WHERE AdapterTypeId=0")

WScript.Echo "Enabling WoL for the following adapters:"

For Each objNetworkAdapter In colNetworkAdapters
            WScript.Echo "  " & objNetworkAdapter.Name & " [" & objNetworkAdapter.MACAddress & "]"

            strNetworkAdapterID = UCase(objNetworkAdapter.PNPDeviceID)

            'Query for all of the MSPower_DeviceWakeEnable classes
            Dim colPowerWakeEnables
            Dim objPowerWakeEnable

            Set colPowerWakeEnables = GetObject("WinMgmts:{impersonationLevel=impersonate}//./root/wmi")_
            .ExecQuery("SELECT * FROM MSPower_DeviceWakeEnable")
            'Compare the PNP Device ID from the network adapter against the MSPower_DeviceEnabled instances
            For Each objPowerWakeEnable In colPowerWakeEnables
                        'We have to compare the leftmost part as MSPower_DeviceEnabled.InstanceName contains an instance suffix
                        strDevInstanceName = UCase(Left(objPowerWakeEnable.InstanceName, Len(strNetworkAdapterID)))
                        'Match found, enable WOL
                        If StrComp(strDevInstanceName, strNetworkAdapterID)=0 Then
                                    objPowerWakeEnable.Enable = True
                                    objPowerWakeEnable.Put_           'Required to write the value back to the object
                        End     If
            Next
            'Query for all of the MSNdis_DeviceWakeOnMagicPacketOnly classes
            Dim colMagicPacketOnlys
            Dim objMagicPacketOnly
            Set colMagicPacketOnlys = GetObject("WinMgmts:{impersonationLevel=impersonate}//./root/wmi")_
            .ExecQuery("SELECT * FROM MSNdis_DeviceWakeOnMagicPacketOnly")
            'Compare the PNP Device ID from the network adapter against the MSNdis_DeviceWakeOnMagicPacketOnly instances
            For Each objMagicPacketOnly In colMagicPacketOnlys
                        'We have to compare the leftmost part as MSNdis_DeviceWakeOnMagicPacketOnly.InstanceName contains an instance suffix
                        strDevInstanceName = UCase(Left(objMagicPacketOnly.InstanceName, Len(strNetworkAdapterID)))
                        'Match found, enable WOL for Magic Packets only
                        If StrComp(strDevInstanceName, strNetworkAdapterID)=0 Then
                                    objMagicPacketOnly.EnableWakeOnMagicPacketOnly = True  'Set to false if you wish to wake on magic packets AND wake patterns
                                    objMagicPacketOnly.Put_             'Required to write the value back to the object
                        End     If
            Next
Next

 

‘vbscript end

What kind of Data Will be flow between the Sites

 

Child sites send the following information to their direct parent sites:

1. Discovery information
2. Inventory information
3. Site control information
4. Status messages

The Data collected from a child site to a parent site are listed here:

1. Discovery data records (DDRs)
2. Inventory data
3. License balancing data
4. Site control files
5. Status messages

The Data passed from a parent site to its associated child sites are listed here

1. Advertisements
2. Collections
3. Package definitions
4. Site control files
5. Software metering data

What is a Central Site?

 

A central site has no parent site. Typically, a central site has child and grandchild sites and aggregates all of their client information to provide centralized management and reporting. A site with no parent and no child site is still called a central site although it is also referred to as a stand-alone site.

A central site can manage all SMS sites which exist beneath it in the SMS hierarchy.
All database information is collected at the SMS database of the central site. Information is passed from the child site to the parent site.
The central site can pass information down the SMS site hierarchy, to each of its child sites.

It is recommended that you install a server locator point and a reporting point site system at the central site because site database information propagates from child sites to the central site. In large organizations, central sites typically do not manage SMS clients.

Distribution Points and mystery of it’s folders

When a DP Role Enabled we can see at least four folders.

 

1.SMSPKG ==>.PCK & *.DLX *.DLT.x
2.SMSPKGX$ ==> Packages Folders & Source
3.SMSPKGSIG ==> Contains .Tar files
4.SMSSIG$  Contains .Tar files

Move or delete SMSPKGSIG folder: -

SCCM2007 creates a folder "SMSPKGSIG" on the drive where the SCCM ProgramFiles are installed.
To move the folder to another drive, you have to do the following steps:

• Stop all SCCM related services (or at least SMS_EXECUTIVE, SMS_SITE_COMPONENT_MANAGER, SMS_SITE_VSS_WRITER)
• Edit the registry key: HKLM\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER\Signature Manager\SignatureRepository = <NewDrive>:\SMSPKGSIG
• Move the folder SMSPKGSIG to the new drive
• Start the SCCM services (SMS_SITE_VSS_WRITER, SMS_SITE_COMPONENT_MANAGER, SMS_EXECUTIVE, SMS_SITE_VSS_WRITER)

Note: Do not move the "SMSSIG$" folder, this procedure is only for the "SMSPKGSIG" folder...
Caution: This is not an official/supported procedure... implementation at your own risk .

How can I move the SMSPKG folder? If smspkg folder fileld with low disk space?

- under Site Settings, Component Configuration, Software Distribution, "Location of stored packages", change it to (in your case) E:\

- Update a package (which doesn't have a .pkg in c:\smspkg already). If I didn't miss any steps, you should get an smspkg on E:\, and it'll store any new compressed files there from now on.

- When you are comfortable doing so, delete the c:\smspkg folder & files.

Monitor Site Status, component status, sms_distribution_manager for any errors, etc.

What Happens if Package Source version not changing? Targeted stays at “1”, Installed goes to “0”, and Retrying probably goes to “1” but Source Version will still stay the same?

Resolution :

a. To resolve the problem now the PCK files need to be manually copied from the parent server (\\<serverName>\sms_cpsg$\<PKG ID>.pck) to the target server (using the same sms_cpsg$ share). 

b.Once the PCK file is back on the server(s) the package can be updated again and everything should be fine. 

Note: only the PCK file needs to be copied, all files with the *.DLT and *.DLT.x extension can be ignored. 

SMSPKG folder on the Primary/Secondary sites contains the compressed PCK files for all the package that were push to them. SMS/SCCM copies these PCK files to sites first and then extracts them on the distribution point.

Yes it is true that it may not be really efficient with disk space, but this is how SMS/SCCM are designed and I guess this was designed like this to save the network bandwidth and to use delta replication.

If there any package that you are sure you will never ever update, then you can delete the PCK files for those package from the sites. Do not remove the PCK files of the packages that may need to be updated.

ACT – Application Compatibility TOOL Tutorial

http://www.msigeek.com/4907/application-compatibility-toolkit-5-5-guides-how-to-tutorials

Who is deleted my DNS records?

Read here http://blogs.technet.com/b/networking/archive/2011/08/17/tracking-dns-record-deletion.aspx

Choose SCCM DP Vs Secondary site Vs BDP

1) Implementing the Secondary site

Pros:-

    Ø  Traffic  can be compressed/ Scheduled/Throttled & rate limit on the  address

Ø  Secondary sites do not require additional Configuration Manager 2007 server licenses.

Ø  Secondary sites do not require an additional SQL Server database at the secondary site.

Ø  Clients can be managed across a slow network connection link, such as a wide area network (WAN) connection between sites, without the need to configure client agent settings.

Ø  Secondary sites can have management points (called proxy management points) to help prevent client reporting information, such as inventory reports and status messages, from traversing slow network connections to the primary site.

Ø  Remote sites can be managed centrally from a parent primary site without the need for an on-site administrator at the secondary site. Less administration when compared with primary sites, After enabling client push binaries can be pushed from here.

 

Cons:-

Ø  Required a server OS

Recommendations: - below are the direct links from Microsoft

http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

2) Implementing the Distribution points:-

Pros: -

Ø  Distribution points can be configured as Protected DP

Ø  Can configure DP Groups for easy selection of DP’s

Cons: -

Ø  DP’s always a SMB copy (that cannot be scheduled, compressed or throttled).

Ø  Required a Server OS and Drive space

Ø  Up to 100 per site, each capable of supporting up to 4,000 clients

 

Recommendations: - below are the direct links from Microsoft

http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

3) Implementing the BDP’s:-

 

Pros:-

Ø  Can be configured on any SCCM Client OS (Server and Workstation systems)

Ø  Communication will happened over the BITS and can be resumed

Ø  Computer Client Agent Properties can be configured with BITS Throttle period

Ø  Content can be set to on demand for clients

Ø  Can have multiple BDP’s

Ø  Will fit for Branch offices where 2 -100 systems

Ø  Will download the package from Standard DP

Cons:-

Ø  Branch Distribution Points cannot be placed on server shares

Limitations:

 

Ø  Up to 2,000 per site, each capable of supporting up to 100 clients

 

Recommendations: - below are the direct links from Microsoft

 http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

 

My recommendations are:-

 

Number of Systems	Recommended Role
50 – above 150	If you don’t care about up & downwards bandwidth then choose DP
2 - 100	BDP - Protected
100 above	Secondary site

if there is a below 100 systems then just go for BDP role on Server based OS

only Desktops in collection

only Desktops in collection

 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes != "10"

WMI Fix Batch file to run on multiple systems

@echo off
%windir%\system32\wbem\winmgmt /clearadap
%windir%\system32\wbem\winmgmt /kill
%windir%\system32\wbem\winmgmt /unregserver
%windir%\system32\wbem\winmgmt /reserver
%windir%\system32\wbem\winmgmt /resyncperf
net stop winmgmt /y
if exist %windir%\system32\wbem\repository.old rmdir /s /q %windir%\system32\wbem\repository.old
ren %windir%\system32\wbem\repository repository.old
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
for /f %%s in (‘dir /b /s %windir%\system32\wbem\*.dll’) do regsvr32 /s %%s
for /f %%s in (‘dir /b /s %windir%\system32\wbem\*.mof’) do mofcomp %%s
for /f %%s in (‘dir /b %windir%\system32\wbem\*.mfl’) do mofcomp %%s
net start winmgmt
%windir%\system32\wbem\wmiprvse /regserver

Save above batch file as wmifix.bat and run with the PSexec.exe with below command line

 

psexec @list.txt -c c:\scripts\wmifix.cmd

List.txt

Add list of computers to the list.txt file which you have trouble.