At some point you may want to change the product key of your windows 2003 server OEM version with a VLK key.
This can be done with two major steps:
1. Determine the channel that your copy of Windows Server 2003 was obtained through
http://support.microsoft.com/kb/889713/en-us
2. Change the Volume Licensing product key
Part 1. Determine the channel that your copy of Windows Server 2003 was obtained through
About Product IDs
All Windows Server 2003 products require the end user to type a Product Key during installation. A unique Product ID (PID) is generated when you run the Windows Server 2003 Setup program. After the Product Key is validated in the Setup program, the Setup program builds the 20-digit PID. The PID is assigned to the computer.
A PID contains the following information:
The first five characters of the PID indicate the Microsoft Product Code (MPC).
The three characters after the MPC indicate the channel ID.
To find your current PID:
Right-click My Computer, and then click Properties.
On the General tab, the PID appears in the Registered to box.
Some MPC codes for Windows Server 2003
Standard Edition 32 bit retail, 69712-000
Standard Edition 32 bit volume licensing, 69712-640
Standard Edition R2, 32 bit volume licensing, 69712-650
Standard Edition 32 bit OEM, 69712-OEM
Enterprise Edition 32 bit retail, 69713-000
Enterprise Edition 32 bit volume licensing, 69713-640
Enterprise Edition R2, 32 bit volume licensing, 69713-650
Enterprise Edition 32 bit OEM, 69713-OEM
More MPC codes please refer to MS KB:
http://support.microsoft.com/kb/889713/en-us
Part 2: change Volume Licensing product key for windows 2003
From part 1 you know what you currently have, then you can change it to the correct VL Key.
KB article 328874 explains how to do it for XP, the good news is, same method works for any version of 2003. So check this out:
http://support.microsoft.com/kb/328874
Here are the steps:
Deactivate Windows
Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
In the navigation pane, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents
In the topic pane, right-click OOBETimer, and then click Modify.
Change at least one digit of this value to deactivate Windows.
Reactivate Windows and add new product key
Click Start, and then click Run.
In the Open box, type the following command, and then click OK.
%systemroot%\system32\oobe\msoobe.exe /a
Click Yes, I want to telephone a customer service representative to activate Windows, and then click Next.
Click Change Product key.
Type the new product key in the New key boxes, and then click Update.If you are returned to the previous window, click Remind me later, and then restart the computer.
Repeat steps 1 and 2 to verify that Windows is activated. You receive the following message:
Windows is already activated. Click OK to exit.
Click OK.
2009-05-24
Setup network from Microsoft Virtual server 2005 R2
Setup network from Microsoft Virtual server 2005 R2
You can configure NAT on the host machine to share your local network with guest virtual machines so that they can be access Internet.With network address translation (NAT), you can configure one or more virtual machines to share the host operating system's Internet connection, as shown in the following table.
1.Install Microsoft Loopback Adapter on the host operating system
2.Enable Internet Connection Sharing on the physical network adapter that is connected to the Internet. Configure ICS so that the physical network adapter shares the connection with Microsoft Loopback Adapter.
3.Create a virtual network and configure it to use Microsoft Loopback Adapter
4.Connect one or more virtual machines to the virtual network that is configured to use Microsoft Loopback Adapter
DHCP server must be in the reserved IP list.An example:1. Host pc setting:Physical NIC: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NICIP: 192.168.10.6subnet: 255.255.255.0Gateway: 192.168.10.1 DNS: 192.168.10.1
MS Loopback adapter is installed on the host pc. ICS is enabled on physical NIC and shares the connection with the loopback adapter.Loopback adapter IP: 192.168.0.1 (leave "default gateway" blank)
2. Guest virtual pc settingVirtual network setting:Start IP: 192.168.0.20End IP: 192.168.0.200DHCP server: 192.168.0.2Default gateway: 192.168.0.1
Note:a. You must leave 16 address as system reserved.For example, if your virtual network is 192.168.0.0, then the first available DHCP IP is 192.168.0.17.b. The virtual DHCP server's IP address must within the reserved IP range.
You can configure NAT on the host machine to share your local network with guest virtual machines so that they can be access Internet.With network address translation (NAT), you can configure one or more virtual machines to share the host operating system's Internet connection, as shown in the following table.
1.Install Microsoft Loopback Adapter on the host operating system
2.Enable Internet Connection Sharing on the physical network adapter that is connected to the Internet. Configure ICS so that the physical network adapter shares the connection with Microsoft Loopback Adapter.
3.Create a virtual network and configure it to use Microsoft Loopback Adapter
4.Connect one or more virtual machines to the virtual network that is configured to use Microsoft Loopback Adapter
DHCP server must be in the reserved IP list.An example:1. Host pc setting:Physical NIC: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NICIP: 192.168.10.6subnet: 255.255.255.0Gateway: 192.168.10.1 DNS: 192.168.10.1
MS Loopback adapter is installed on the host pc. ICS is enabled on physical NIC and shares the connection with the loopback adapter.Loopback adapter IP: 192.168.0.1 (leave "default gateway" blank)
2. Guest virtual pc settingVirtual network setting:Start IP: 192.168.0.20End IP: 192.168.0.200DHCP server: 192.168.0.2Default gateway: 192.168.0.1
Note:a. You must leave 16 address as system reserved.For example, if your virtual network is 192.168.0.0, then the first available DHCP IP is 192.168.0.17.b. The virtual DHCP server's IP address must within the reserved IP range.
2009-05-23
IE7.0 compatibility issue with IE8.0
Problem:
When use Virtual server admin web console, got error:
Message: 'document.getElementById(...)' is null or not an object
Reason:
IE8 seems to have some trouble to work normally with the js controls of Virtual Server 2005, but you can easily make it work by choosing IE8 to work in IE7 compatibility mode.
Just aside to the url you should have a button that seems like a "broken sheet of paper". Click on that and you will be in IE7 compatibility mode, and everything will work fine with Virtual Server.
2009-05-20
ConfigMgr 2007: The Preload Package Tool (PreloadPkgOnSite.exe) Explained
ConfigMgr 2007: The Preload Package Tool (PreloadPkgOnSite.exe) Explained
http://blogs.technet.com/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx
http://blogs.technet.com/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx
How do we refresh a package located on a Branch Distribution Point?
http://blogs.technet.com/carlossantiago/archive/2008/05/16/how-do-we-refresh-a-package-located-on-a-branch-distribution-point.aspx
The short answer is, we can't. That does not mean that we don't have a way to update that package on the Branch Distribution Point (BDP), it just means that we can't refresh them. In SCCM refreshing vs. updating a package has different meanings. When we run the Manage Distribution Points Wizard and select the option to refresh a package on distribution points, we are asking the Distribution Manager service to use the existing compressed version of the package and extract it to the specified distribution points. This is true unless we used the always obtain files from source option on the package properties. When we select the option to update a package, we are asking Distribution Manager to get the files from the source directory, create a new compressed version of the package, possibly send the compressed version to child sites, and then extract the new version to the distribution points. If you are wondering when should we use a refresh vs. an update think about the following scenarios:
Scenario #1
There is a central site in your headquarters office (NY) with primary child sites on remote offices. Software packages are created on the central site. There is a slow WAN connection between the central site and the child sites. One of the child sites is in Dallas and has distribution points in Dallas, Austin, and Houston. There is a hard drive failure on the Houston distribution point and a new hard drive is installed. There is no backup of the hard drive that was replaced since it only contained SCCM packages.
Scenario #2
There is a central site in your headquarters office (NY) with primary child sites on remote offices. Software packages are created on the central site. There is a slow WAN connection between the central site and the child sites. One of the child sites is in Dallas and has distribution points in Dallas, Austin, and Houston. The signature files for the antivirus application used by the company got updated. We updated the package source files and now need to get those files to the distribution points.
In Scenario #1, we could use the refresh package on the Houston distribution point option. The central site server will send an instruction to distribution manager on the Dallas site to extract the local compressed version of the package to the Houston distribution point. This will save time and traffic across the WAN link. In Scenario #2, we need to get new files for a package to the distribution points. In that case we need a new version of the compressed package to be sent over the WAN to the child sites. Distribution Manager on the Dallas child site will get the new compressed package and will then extract it to its local distribution point and the the ones in Austin and Houston.
The above is a very simplified explanation of what happens behind the scenes and I am not going to get in the details of delta replication. That is because this blog is about BDPs, so lets get back on track. If we run the Manage Distribution Points Wizard the first thing we are going to find out if we try to refresh a package on a BDP is that they are not listed in the Wizard. There is no refresh option for the BDPs because distribution manager does not handle packages on BDPs. The BDP role is a client side role. The BDP gets machine policies that tell the client what packages to download and share. Let say that in scenarios #1 and #2 the Houston distribution point is a BDP. In that case the refresh will not work obviously because it is not an option in the admin console. On scenario #1, to get the packages back on the Houston BDP we would have to use update option. On scenario #2, we would also get the new signature files to the Houston BDP by selecting to update the package on the distribution points.
The short answer is, we can't. That does not mean that we don't have a way to update that package on the Branch Distribution Point (BDP), it just means that we can't refresh them. In SCCM refreshing vs. updating a package has different meanings. When we run the Manage Distribution Points Wizard and select the option to refresh a package on distribution points, we are asking the Distribution Manager service to use the existing compressed version of the package and extract it to the specified distribution points. This is true unless we used the always obtain files from source option on the package properties. When we select the option to update a package, we are asking Distribution Manager to get the files from the source directory, create a new compressed version of the package, possibly send the compressed version to child sites, and then extract the new version to the distribution points. If you are wondering when should we use a refresh vs. an update think about the following scenarios:
Scenario #1
There is a central site in your headquarters office (NY) with primary child sites on remote offices. Software packages are created on the central site. There is a slow WAN connection between the central site and the child sites. One of the child sites is in Dallas and has distribution points in Dallas, Austin, and Houston. There is a hard drive failure on the Houston distribution point and a new hard drive is installed. There is no backup of the hard drive that was replaced since it only contained SCCM packages.
Scenario #2
There is a central site in your headquarters office (NY) with primary child sites on remote offices. Software packages are created on the central site. There is a slow WAN connection between the central site and the child sites. One of the child sites is in Dallas and has distribution points in Dallas, Austin, and Houston. The signature files for the antivirus application used by the company got updated. We updated the package source files and now need to get those files to the distribution points.
In Scenario #1, we could use the refresh package on the Houston distribution point option. The central site server will send an instruction to distribution manager on the Dallas site to extract the local compressed version of the package to the Houston distribution point. This will save time and traffic across the WAN link. In Scenario #2, we need to get new files for a package to the distribution points. In that case we need a new version of the compressed package to be sent over the WAN to the child sites. Distribution Manager on the Dallas child site will get the new compressed package and will then extract it to its local distribution point and the the ones in Austin and Houston.
The above is a very simplified explanation of what happens behind the scenes and I am not going to get in the details of delta replication. That is because this blog is about BDPs, so lets get back on track. If we run the Manage Distribution Points Wizard the first thing we are going to find out if we try to refresh a package on a BDP is that they are not listed in the Wizard. There is no refresh option for the BDPs because distribution manager does not handle packages on BDPs. The BDP role is a client side role. The BDP gets machine policies that tell the client what packages to download and share. Let say that in scenarios #1 and #2 the Houston distribution point is a BDP. In that case the refresh will not work obviously because it is not an option in the admin console. On scenario #1, to get the packages back on the Houston BDP we would have to use update option. On scenario #2, we would also get the new signature files to the Houston BDP by selecting to update the package on the distribution points.
SCCm package distribution
When you refresh package data on a Microsoft System Center Configuration Manager 2007 distribution point, the package is copied from the compressed version on the site server but not updated from the original source.
Refreshing the package does not increment the package version.
Updating the distribution point will copy files from the source folder, thus incrementing the package version
Refreshing the package does not increment the package version.
Updating the distribution point will copy files from the source folder, thus incrementing the package version
2009-05-10
List of VHDs on Microsoft VHD Test Drive site
This is where you can download pre-built Virtual Hard Disks, containing Microsoft OS’s and Server Applications like Exchange 2007.
Windows Server 2008 Standard Ed. x86 (full install)
Windows Server 2008 Standard Ed. x64 (full install)
Windows Server 2008 Enterprise Ed. x86 (full install)
Windows Server 2008 Enterprise Ed. x64 (full install)
Windows Server 2008 Standard Ed. x86 (core install)
Windows Server 2008 Standard Ed. x64 (core install)
Windows Server 2008 Enterprise Ed. x86 (core install)
Windows Server 2008 Enterprise Ed. x64 (core install)
Exchange Server 2007 SP1
Windows Server 2003 R2
System Center Configuration Manager 2007 R2
Office SharePoint Server 2007
Forefront codename "Stirling"
System Center Essentials 2007 SP1
Windows Vista
All of the Windows Server 2008 VHDs are designed for Hyper-V, so you’ll need to run them on that platform. Exchange Server, Windows Server 2003 and below (on the list) are designed for Virtual Server 2005 R2 SP1, and the Vista VHD is designed for Virtual PC 2007.
Windows Server 2008 Standard Ed. x86 (full install)
Windows Server 2008 Standard Ed. x64 (full install)
Windows Server 2008 Enterprise Ed. x86 (full install)
Windows Server 2008 Enterprise Ed. x64 (full install)
Windows Server 2008 Standard Ed. x86 (core install)
Windows Server 2008 Standard Ed. x64 (core install)
Windows Server 2008 Enterprise Ed. x86 (core install)
Windows Server 2008 Enterprise Ed. x64 (core install)
Exchange Server 2007 SP1
Windows Server 2003 R2
System Center Configuration Manager 2007 R2
Office SharePoint Server 2007
Forefront codename "Stirling"
System Center Essentials 2007 SP1
Windows Vista
All of the Windows Server 2008 VHDs are designed for Hyper-V, so you’ll need to run them on that platform. Exchange Server, Windows Server 2003 and below (on the list) are designed for Virtual Server 2005 R2 SP1, and the Vista VHD is designed for Virtual PC 2007.
2009-02-12
New group policies for DNS in Windows Server 2003
New group policies for DNS in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;294785
Windows Server 2003 resolves the problem of centralized DNS management by introducing group policies to configure DNS clients. For example, the following parameters are available in Windows Server 2003:
Enable or disable dynamic registration of the DNS records by a clientConfigure DNS suffix search list of the clientsDevolution of the primary DNS suffix in a name resolution processDNS suffix search list
These group policies are at the following location:
Computer Configuration/Administrative Templates/Network/DNS Client Group policy always supersedes the local configuration as well as the DHCP configuration. The only exception to this rule is if the REG_DWORD value DoNotUseGroupPolicyForDisableDynamicUpdate is enabled under the following registry key to disable dynamic DNS registration: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersIf this value exists and it is set to 0x1, then services do not use a group policy value; instead they use locally configured values. If DoNotUseGroupPolicyForDisableDynamicUpdate does not exist or is set to 0x0, services must use the value that is specified by the group policy.
Policy DescriptionsThis section describes the settings' functions, the registry key which is modified on the client, and the valid values for the policy and the registry key. These values are stored on the client is the following registry key: HKEY_LOCAL_MACHINE\Software\Polices\Microsoft\Windows NT\DNSClientPrimary DNS SuffixThis setting specifies the primary DNS suffix for all affected computers. The primary DNS suffix is used in DNS name registration and DNS name resolution. This setting specifies a primary DNS suffix for a group of computers, and prevents users, including administrators, from changing it.
If this setting is disabled or not configured, each computer uses its local primary DNS suffix that is usually the DNS name of the Active Directory domain that it is joined to. However, administrators can use the System tool in Control Panel to change the primary DNS suffix of a computer.
To use this setting, type the entire primary DNS suffix that you want to assign in the text box that is provided (for example, microsoft.com). This setting does not disable the DNS Suffix and NetBIOS Computer Name dialog box that administrators use to change the primary DNS suffix of a computer. However, if an administrator enters a suffix, that suffix is ignored while this setting is enabled.
IMPORTANT: For the changes to this setting to be applied, you must restart Windows Server on all computers that are affected by the setting.
TIP: To change the primary DNS suffix of a computer without setting a policy, click System in Control Panel, click the Network Identification tab, click Properties, click More, and then type a suffix in the Primary DNS suffix of this computer box.
http://support.microsoft.com/default.aspx?scid=kb;en-us;294785
Windows Server 2003 resolves the problem of centralized DNS management by introducing group policies to configure DNS clients. For example, the following parameters are available in Windows Server 2003:
Enable or disable dynamic registration of the DNS records by a clientConfigure DNS suffix search list of the clientsDevolution of the primary DNS suffix in a name resolution processDNS suffix search list
These group policies are at the following location:
Computer Configuration/Administrative Templates/Network/DNS Client Group policy always supersedes the local configuration as well as the DHCP configuration. The only exception to this rule is if the REG_DWORD value DoNotUseGroupPolicyForDisableDynamicUpdate is enabled under the following registry key to disable dynamic DNS registration: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersIf this value exists and it is set to 0x1, then services do not use a group policy value; instead they use locally configured values. If DoNotUseGroupPolicyForDisableDynamicUpdate does not exist or is set to 0x0, services must use the value that is specified by the group policy.
Policy DescriptionsThis section describes the settings' functions, the registry key which is modified on the client, and the valid values for the policy and the registry key. These values are stored on the client is the following registry key: HKEY_LOCAL_MACHINE\Software\Polices\Microsoft\Windows NT\DNSClientPrimary DNS SuffixThis setting specifies the primary DNS suffix for all affected computers. The primary DNS suffix is used in DNS name registration and DNS name resolution. This setting specifies a primary DNS suffix for a group of computers, and prevents users, including administrators, from changing it.
If this setting is disabled or not configured, each computer uses its local primary DNS suffix that is usually the DNS name of the Active Directory domain that it is joined to. However, administrators can use the System tool in Control Panel to change the primary DNS suffix of a computer.
To use this setting, type the entire primary DNS suffix that you want to assign in the text box that is provided (for example, microsoft.com). This setting does not disable the DNS Suffix and NetBIOS Computer Name dialog box that administrators use to change the primary DNS suffix of a computer. However, if an administrator enters a suffix, that suffix is ignored while this setting is enabled.
IMPORTANT: For the changes to this setting to be applied, you must restart Windows Server on all computers that are affected by the setting.
TIP: To change the primary DNS suffix of a computer without setting a policy, click System in Control Panel, click the Network Identification tab, click Properties, click More, and then type a suffix in the Primary DNS suffix of this computer box.
what is the difference between Difference between "Primary DNS Suffix" and "Connection specific DNS Suffix"??
http://www.experts-exchange.com/Networking/Misc/Q_21729492.html
Question:
what is the difference between Difference between "Primary DNS Suffix" and "Connection specific DNS Suffix"??
This information is presented whenever i perform a "ipconfig -all", such as:
C:\>ipconfig -all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : webserver
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : scaa.org
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : scaa.org
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-30-1B-3E-4E-19
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.1
DHCP Server . . . . . . . . . . . : 10.0.1.10
DNS Servers . . . . . . . . . . . : 10.0.1.10
64.80.125.114
Primary WINS Server . . . . . . . : 10.0.1.10
Answer 1:
You assign the Primary DNS Suffix and your DHCP device assigns Connection specific DNS Suffix
Answer 2:
True, but not complete.
Primary DNS Suffix is set for the entire computer and will be used on any network adaptor on which no Connection-specific DNS Suffix has been defined.
The Connection-specific DNS Suffix allows us to overide the Primary for a specific network adaptor so that when your computer registers itself with the DNS server it's presently using, it will register with a well-formed fully qualified domain name (FQDN). The thing that MS calls DNS suffix is really just everything to the right of the first dot in a FQDN.
Imagine your company-supplied laptop computer has FQDN "joe.boston.corpX.com" and it's part of an Active Directory domain at the office. It's Primary suffix is "boston.corpX.com" and it's name is "joe." When you boot it up at the office, it will DHCPDISCOVER an IP address and the AD DC's DHCP server will respond, then your computer will register itself with the DNS server on that AD DC using it's FQDN.
If you use a VPN Client on the road, though, so you can connect to your company's network from the hotel broadband service. It may be smarter (or neccessary) to have your computer register itself as joe.remote.corpX.com with the RAS server in your network. That's where the Connection-specific DNS Suffix comes in. When you installed that VPN Client Software (or your IT team did), it created another network adaptor and the Connection-specific DNS suffix on that one is ... yep, remote.corpX.com and all is well.
In general use, we don't use it. On systems with only one network adapator, just leave it blank. Unless someone in a higher paygrade that knows why you should change it tells you to, that is... :-)
Question:
what is the difference between Difference between "Primary DNS Suffix" and "Connection specific DNS Suffix"??
This information is presented whenever i perform a "ipconfig -all", such as:
C:\>ipconfig -all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : webserver
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : scaa.org
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : scaa.org
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-30-1B-3E-4E-19
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.1
DHCP Server . . . . . . . . . . . : 10.0.1.10
DNS Servers . . . . . . . . . . . : 10.0.1.10
64.80.125.114
Primary WINS Server . . . . . . . : 10.0.1.10
Answer 1:
You assign the Primary DNS Suffix and your DHCP device assigns Connection specific DNS Suffix
Answer 2:
True, but not complete.
Primary DNS Suffix is set for the entire computer and will be used on any network adaptor on which no Connection-specific DNS Suffix has been defined.
The Connection-specific DNS Suffix allows us to overide the Primary for a specific network adaptor so that when your computer registers itself with the DNS server it's presently using, it will register with a well-formed fully qualified domain name (FQDN). The thing that MS calls DNS suffix is really just everything to the right of the first dot in a FQDN.
Imagine your company-supplied laptop computer has FQDN "joe.boston.corpX.com" and it's part of an Active Directory domain at the office. It's Primary suffix is "boston.corpX.com" and it's name is "joe." When you boot it up at the office, it will DHCPDISCOVER an IP address and the AD DC's DHCP server will respond, then your computer will register itself with the DNS server on that AD DC using it's FQDN.
If you use a VPN Client on the road, though, so you can connect to your company's network from the hotel broadband service. It may be smarter (or neccessary) to have your computer register itself as joe.remote.corpX.com with the RAS server in your network. That's where the Connection-specific DNS Suffix comes in. When you installed that VPN Client Software (or your IT team did), it created another network adaptor and the Connection-specific DNS suffix on that one is ... yep, remote.corpX.com and all is well.
In general use, we don't use it. On systems with only one network adapator, just leave it blank. Unless someone in a higher paygrade that knows why you should change it tells you to, that is... :-)
2009-01-28
How to open Control Panel Items from Command Line in Vista
How To Make Shortcuts to Control Panel Pages in Vista
http://www.dailygeeks.com/howto/how-to-make-shortcuts-to-control-panel-pages-in-vista/
How to open Control Panel Items from Command Line in Vista
http://www.nibbleguru.com/problem/5074-how-open-control-panel-items-command-line-vista
New Vista Syntax for Opening Control Panel Items from the Command-line
http://www.howtogeek.com/howto/windows-vista/new-vista-syntax-for-opening-control-panel-items-from-the-command-line/
Accessibility Options, access.cpl
Add/Remove Programs, appwiz.cpl
Add Hardware Wizard, hdwwiz.cpl
Automatic Updates, wuaucpl.cpl
Bluetooth Properties, bthprops.cpl
Display Properties, desk.cpl
Firewall Properties, firewall.cpl
Game Controllers, joy.cpl
Internet Options, inetcpl.cpl
iSCSI Initiator, iscsicpl.cpl
Java Control Panel, jpicpl32.cpl (java install folder\javacpl.exe)
Licensing Mode, liccpa.cpl
Mouse Properties, main.cpl
Network Connections, ncpa.cpl
Network Setup Wizard, netsetup.cpl
ODBC Properties, odbccp32.cpl
Power Options, powercfg.cpl
Regional and Language Options, intl.cpl
Sound and Audio Devices, mmsys.cpl
Stored Passwords, keymgr.cpl
System Properties, sysdm.cpl
Telephone and Modem Properties, telephon.cpl
Time and Date Settings, timedate.cpl
User Accounts, nusrmgr.cpl
Windows Security Center, wscui.cpl
Wireless Link, irprops.cpl
http://www.dailygeeks.com/howto/how-to-make-shortcuts-to-control-panel-pages-in-vista/
How to open Control Panel Items from Command Line in Vista
http://www.nibbleguru.com/problem/5074-how-open-control-panel-items-command-line-vista
New Vista Syntax for Opening Control Panel Items from the Command-line
http://www.howtogeek.com/howto/windows-vista/new-vista-syntax-for-opening-control-panel-items-from-the-command-line/
Accessibility Options, access.cpl
Add/Remove Programs, appwiz.cpl
Add Hardware Wizard, hdwwiz.cpl
Automatic Updates, wuaucpl.cpl
Bluetooth Properties, bthprops.cpl
Display Properties, desk.cpl
Firewall Properties, firewall.cpl
Game Controllers, joy.cpl
Internet Options, inetcpl.cpl
iSCSI Initiator, iscsicpl.cpl
Java Control Panel, jpicpl32.cpl (java install folder\javacpl.exe)
Licensing Mode, liccpa.cpl
Mouse Properties, main.cpl
Network Connections, ncpa.cpl
Network Setup Wizard, netsetup.cpl
ODBC Properties, odbccp32.cpl
Power Options, powercfg.cpl
Regional and Language Options, intl.cpl
Sound and Audio Devices, mmsys.cpl
Stored Passwords, keymgr.cpl
System Properties, sysdm.cpl
Telephone and Modem Properties, telephon.cpl
Time and Date Settings, timedate.cpl
User Accounts, nusrmgr.cpl
Windows Security Center, wscui.cpl
Wireless Link, irprops.cpl
2009-01-27
借助路由器，实现iAMT的本地管理
借助路由器，实现iAMT的本地管理
我们在开发支持Intel主动管理技术的控制台时，访问管理引擎（ME）提供的Web Service接口有两种方式，一种是通过网络访问，另外一种是本机直接访问。但是本机访问有比较多的限制，大部分iAMT功能接口对本地应用程序来说是不可用的，比如CircuitBreak，AgentPresence，SecurityAdministration等等。那么在没有两台机器的情况下，如何实现在iAMT机器的主机操作系统上就能对iAMT所有特性进行操作呢？
经过笔者的一些简单实验，我们只需要一台普通的路由器就能做得到。比如，一般的ADSL接入设备，无线路由器，或者自己用Linux搭建的网关都行。大概的原理是这样的：给iAMT和Host OS配置不同网段的IP地址，都将网关指向路由器；然后在路由器上设定所需的路由；在Host OS上的应用程序访问iAMT IP地址时，网络包首先被发送到默认网关，也就是路由器，然后路由器根据自身的路由表将网络包路由到iAMT，iAMT的返回结果同样也是先发送到路由器，然后由路由器再将网络包路由回Host OS。如下图所示。
在上图中，我们将一台Intel Core 2 vPro机器（内建iAMT功能）的主机操作系统IP地址配置为192.168.2.10，网关指向192.168.1.1，由于这里网关和主机地址不在同一个网段，只能手动配置静态IP了；将底层的iAMT的IP地址配置为192.168.1.10，网关指向192.168.1.1。
这里的路由器兼做网关（我们使用的普通路由器都是这么用的），LAN口配置的IP地址是192.168.1.1；为了使得路由器能够将iAMT返回的数据包回送给Host OS，我们需要在路由表里面增加一项： Destination：192.168.2.0 Netmask: 255.255.255.0 Gateway: 0.0.0.0 (如果是Windows做路由器, 这里就是192.168.1.1)
另外，如果路由器支持LAN接口配置多个IP地址，那只需要为路由器LAN口再配置一个IP地址：192.168.2.1，上面那条路由就能自动加入到路由表；这时候，Host OS的网关可以设置为192.168.2.1。这样，我们就可以在Host OS上通过直接访问底层iAMT的IP来访问iAMT的功能了。比如，通过IE打开：http://192.168.1.10:16992，就可以见到我们熟悉的iAMT WEBUI的登陆界面了。
我在一台LinkSys的无线路由器，和一台Windows 2003 Server的网关上测试过，上述的方法都可以成功。如果你有兴趣，欢迎一起交流探讨。
经过笔者的一些简单实验，我们只需要一台普通的路由器就能做得到。比如，一般的ADSL接入设备，无线路由器，或者自己用Linux搭建的网关都行。大概的原理是这样的：给iAMT和Host OS配置不同网段的IP地址，都将网关指向路由器；然后在路由器上设定所需的路由；在Host OS上的应用程序访问iAMT IP地址时，网络包首先被发送到默认网关，也就是路由器，然后路由器根据自身的路由表将网络包路由到iAMT，iAMT的返回结果同样也是先发送到路由器，然后由路由器再将网络包路由回Host OS。如下图所示。
在上图中，我们将一台Intel Core 2 vPro机器（内建iAMT功能）的主机操作系统IP地址配置为192.168.2.10，网关指向192.168.1.1，由于这里网关和主机地址不在同一个网段，只能手动配置静态IP了；将底层的iAMT的IP地址配置为192.168.1.10，网关指向192.168.1.1。
这里的路由器兼做网关（我们使用的普通路由器都是这么用的），LAN口配置的IP地址是192.168.1.1；为了使得路由器能够将iAMT返回的数据包回送给Host OS，我们需要在路由表里面增加一项： Destination：192.168.2.0 Netmask: 255.255.255.0 Gateway: 0.0.0.0 (如果是Windows做路由器, 这里就是192.168.1.1)
另外，如果路由器支持LAN接口配置多个IP地址，那只需要为路由器LAN口再配置一个IP地址：192.168.2.1，上面那条路由就能自动加入到路由表；这时候，Host OS的网关可以设置为192.168.2.1。这样，我们就可以在Host OS上通过直接访问底层iAMT的IP来访问iAMT的功能了。比如，通过IE打开：http://192.168.1.10:16992，就可以见到我们熟悉的iAMT WEBUI的登陆界面了。
我在一台LinkSys的无线路由器，和一台Windows 2003 Server的网关上测试过，上述的方法都可以成功。如果你有兴趣，欢迎一起交流探讨。
Out of Band Management简介
http://blogs.technet.com/msdchina/archive/2009/01/08/out-of-band-management-sccm-2007-.aspx
Out of Band Management简介 —— SCCM 2007 Out of Band Management专题系列之一
Out of Band Management正在逐步成为IT管理的主流技术，本专题系列计划就SCCM 2007中Out of Band Management feature做一些介绍和探讨，来帮助读者了解并使用SCCM 2007中的Out of Band Management技术，系列将包括简介，使用，调错等专题文章。
Out of Band Management简介
Out of Band Management是指带外管理技术，是一种不依赖于操作系统就可对目标机器进行管理的技术，目前Intel的AMT（Active Management Technology）和DASH标准（Desktop and mobile Architecture for System Hardware）都提供了Out of Band Management的支持。 在SCCM 2007 SP1，我们将AMT技术整合到SCCM产品之中，此模块被称为Out of Band Management feature。上海研发团队主导了这部分功能的所有设计，开发工作。
SCCM Out of Band Management结合了AMT在硬件层面的强大功能，并依托了SCCM平台中强有力的企业机器管理模式，为企业提供了灵活、便捷、强大的远程唤醒、远程技术支持、资产管理、、灾难恢复等功能。
Overview of Out of Band Management
Topic last updated—May 2008
http://technet.microsoft.com/en-us/library/cc161963.aspx
Out of band management in Configuration Manager 2007 SP1 provides powerful management control for computers that have the Intel vPro chip set and Intel Active Management Technology (Intel AMT) firmware versions 3.2.1 or later.
Out of band management allows an administrator to connect to a computer's management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.
Out of band management supplements in-band management. While in-band management supports a wider range of operations because its environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.
Out of Band Management简介 —— SCCM 2007 Out of Band Management专题系列之一
Out of Band Management正在逐步成为IT管理的主流技术，本专题系列计划就SCCM 2007中Out of Band Management feature做一些介绍和探讨，来帮助读者了解并使用SCCM 2007中的Out of Band Management技术，系列将包括简介，使用，调错等专题文章。
Out of Band Management简介
Out of Band Management是指带外管理技术，是一种不依赖于操作系统就可对目标机器进行管理的技术，目前Intel的AMT（Active Management Technology）和DASH标准（Desktop and mobile Architecture for System Hardware）都提供了Out of Band Management的支持。 在SCCM 2007 SP1，我们将AMT技术整合到SCCM产品之中，此模块被称为Out of Band Management feature。上海研发团队主导了这部分功能的所有设计，开发工作。
SCCM Out of Band Management结合了AMT在硬件层面的强大功能，并依托了SCCM平台中强有力的企业机器管理模式，为企业提供了灵活、便捷、强大的远程唤醒、远程技术支持、资产管理、、灾难恢复等功能。
Overview of Out of Band Management
Topic last updated—May 2008
http://technet.microsoft.com/en-us/library/cc161963.aspx
Out of band management in Configuration Manager 2007 SP1 provides powerful management control for computers that have the Intel vPro chip set and Intel Active Management Technology (Intel AMT) firmware versions 3.2.1 or later.
Out of band management allows an administrator to connect to a computer's management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.
Out of band management supplements in-band management. While in-band management supports a wider range of operations because its environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.
2009-01-22
Content location request for apps package failed. (Code 0x80040102)
Got error during SCCM deployment:
Content location request for apps package failed. (Code 0x80040102)
Information from Microsoft about this code:
Error code 0x80040102: No content location returned for the given package
solution:
Check the server side to make sure the package is distributed to at least one distribution point. Also check whether advertisement allows the task sequence to fall back to remote distribution point when there is no local distribution point
Troubleshooting Operating System Deployment Using Custom Error Codes
http://technet.microsoft.com/en-us/library/bb735886.aspx
Custom Error Codes for Configuration Manager 2007
http://technet.microsoft.com/en-us/library/bb632794.aspx
This fixed my problem:
Configuration manager->site database->computer management->software distribution -> advertisements -> right click on the advertisement you want to edit and choose properties -> "distribution points" Tab -> tick "when no local distribution points is available, use a remote distribution point" and "when no protected distribution point is available, use an unprotected distribution point.
Save and restart the build again.
Content location request for apps package failed. (Code 0x80040102)
Information from Microsoft about this code:
Error code 0x80040102: No content location returned for the given package
solution:
Check the server side to make sure the package is distributed to at least one distribution point. Also check whether advertisement allows the task sequence to fall back to remote distribution point when there is no local distribution point
Troubleshooting Operating System Deployment Using Custom Error Codes
http://technet.microsoft.com/en-us/library/bb735886.aspx
Custom Error Codes for Configuration Manager 2007
http://technet.microsoft.com/en-us/library/bb632794.aspx
This fixed my problem:
Configuration manager->site database->computer management->software distribution -> advertisements -> right click on the advertisement you want to edit and choose properties -> "distribution points" Tab -> tick "when no local distribution points is available, use a remote distribution point" and "when no protected distribution point is available, use an unprotected distribution point.
Save and restart the build again.
2009-01-12
Joining a domain during an SCCM OS deployment
Inside ConfigMgr 07 Operating System Deployment
http://blogs.technet.com/inside_osd/Default.aspx?p=2
Joining a Domain: Epilogue
http://blogs.technet.com/inside_osd/archive/2007/06/29/joining-a-domain-epilogue.aspx
Joining a Domain, Part 2
http://blogs.technet.com/inside_osd/archive/2007/06/26/joining-a-domain-part-2.aspx
Joining a domain during an OS deployment
http://blogs.technet.com/inside_osd/archive/2007/06/22/joining-a-domain-during-an-os-deployment.aspx
http://blogs.technet.com/inside_osd/Default.aspx?p=2
Joining a Domain: Epilogue
http://blogs.technet.com/inside_osd/archive/2007/06/29/joining-a-domain-epilogue.aspx
Joining a Domain, Part 2
http://blogs.technet.com/inside_osd/archive/2007/06/26/joining-a-domain-part-2.aspx
Joining a domain during an OS deployment
http://blogs.technet.com/inside_osd/archive/2007/06/22/joining-a-domain-during-an-os-deployment.aspx
2009-01-09
Ports used by Configuration Manager
Ports used by Configuration Manager
http://technet.microsoft.com/en-us/library/bb632618.aspx
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
You should also take into account that workstations may (and should) have Windows Firewall enabled.
Firewall Settings for Configuration Manager Clients
http://technet.microsoft.com/en-us/library/bb694088.aspx
Also clients need to be installed first. If you plan to use Client Push, I believe ports for RPC and Kerberos should be opened. Or you can use logon scripts.
However the ports used depend on the features that you plan to use in your infrastructure. Best option in my opinion is to try to implement Native Mode. Then all the communication with the clients will use 443 (SSL).
As a matter of fact I am struggling to configure it myself right now :-)
More info here:
Choose between Native Mode and Mixed Mode
http://technet.microsoft.com/en-us/library/bb632431.aspx
http://technet.microsoft.com/en-us/library/bb632618.aspx
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
You should also take into account that workstations may (and should) have Windows Firewall enabled.
Firewall Settings for Configuration Manager Clients
http://technet.microsoft.com/en-us/library/bb694088.aspx
Also clients need to be installed first. If you plan to use Client Push, I believe ports for RPC and Kerberos should be opened. Or you can use logon scripts.
However the ports used depend on the features that you plan to use in your infrastructure. Best option in my opinion is to try to implement Native Mode. Then all the communication with the clients will use 443 (SSL).
As a matter of fact I am struggling to configure it myself right now :-)
More info here:
Choose between Native Mode and Mixed Mode
http://technet.microsoft.com/en-us/library/bb632431.aspx
2008-12-31
SMS2003部署及troubleshooting
http://struggle.blog.51cto.com/333093/79354
详解SMS2003部署Windows 2003
http://www.winsvr.org/info/info.php?sessid=&infoid=32&page=1
SMS 2003安装配置系列之一:SMS 2003主站点安装指南
http://www.ixpub.net/archiver/tid-658413.html
解读SMS2003日志文件
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx#EWEAC
Clients Frequently Asked Questions
http://www.ixpub.net/thread-658378-1-7.html
如何解决在 Systems Management Server 2003 高级客户端推送安装问题
http://www.microsoft.com/technet/scriptcenter/guide/sas_roa_overview.mspx?mfr=true
Microsoft Windows 2000 Scripting Guide
http://technet.microsoft.com/en-us/library/cc179974%28TechNet.10%29.aspx
Scripting in SMS
http://support.microsoft.com/kb/883620
You cannot install Advanced Client when your Systems Management Server 2003 does not use Active Directory or when the schema for Active Directory has not been extended
http://support.microsoft.com/kb/925282
How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003
http://www.tek-tips.com/viewthread.cfm?qid=1151166&page=1
解决sms客户端无法安装的问题，如何检查DC之间的复制是否成功。
http://technet.microsoft.com/en-us/library/cc181833%28TechNet.10%29.aspx
technet resource: Systems Management Server 2003
详解SMS2003部署Windows 2003
http://www.winsvr.org/info/info.php?sessid=&infoid=32&page=1
SMS 2003安装配置系列之一:SMS 2003主站点安装指南
http://www.ixpub.net/archiver/tid-658413.html
解读SMS2003日志文件
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx#EWEAC
Clients Frequently Asked Questions
http://www.ixpub.net/thread-658378-1-7.html
如何解决在 Systems Management Server 2003 高级客户端推送安装问题
http://www.microsoft.com/technet/scriptcenter/guide/sas_roa_overview.mspx?mfr=true
Microsoft Windows 2000 Scripting Guide
http://technet.microsoft.com/en-us/library/cc179974%28TechNet.10%29.aspx
Scripting in SMS
http://support.microsoft.com/kb/883620
You cannot install Advanced Client when your Systems Management Server 2003 does not use Active Directory or when the schema for Active Directory has not been extended
http://support.microsoft.com/kb/925282
How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003
http://www.tek-tips.com/viewthread.cfm?qid=1151166&page=1
解决sms客户端无法安装的问题，如何检查DC之间的复制是否成功。
http://technet.microsoft.com/en-us/library/cc181833%28TechNet.10%29.aspx
technet resource: Systems Management Server 2003
Force SCCM client to check advertisements
System ManagementCustomize SMS Using Local Policies
http://technet.microsoft.com/en-us/magazine/2006.09.customizesms.aspx
Force Task Sequence Execution without Advertisement
http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/298b32f6-746c-473a-b7ce-6bb51cfe1270/
Force SCCM Client to Check for New Advertisements
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a1066dfb-a71e-4e52-b7b7-c225ea0935a4/
http://technet.microsoft.com/en-us/magazine/2006.09.customizesms.aspx
Force Task Sequence Execution without Advertisement
http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/298b32f6-746c-473a-b7ce-6bb51cfe1270/
Force SCCM Client to Check for New Advertisements
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a1066dfb-a71e-4e52-b7b7-c225ea0935a4/
Control SCCM client actions by scripting
The Advanced Client, is scriptable. You can use the CPApplet locally on the client or you can use WMI to do things remotely. On thing you'll often need is the triggering of an action. There are loads of samples in this forum meanwhile how to do it. Here is an overview of the actions available and their respective ScheduledMessageIDs which you will need to trigger them remotely.
(From http://www.myitforum.com/articles/8/view.asp?id=6757)
Hardware Inventory Cycle
CPApplet Name: Hardware Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000001}
Software Inventory Cycle
CPApplet Name: Software Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000002}
Discovery Data Collection Cycle
CPApplet Name: Discovery Data Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000003}
File Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000010}
ID MIF Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000011}
Machine Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate Machine Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000021} RequestAssignments Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000022} Evaluate Policy Resource Type=’Machine’
The Machine Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context with no corresponding Client Actions.
ScheduledMessageID: {00000000-0000-0000-0000-00000040} CleanupPolicy Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000042} ValidateAssignments Resource Type=’Machine’
User Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate User Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000026} RequestAssignments Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000027} Evaluate Policy Resource Type=’User’
The User Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context.
ScheduledMessageID: {00000000-0000-0000-0000-00000041} CleanupPolicy Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000043} ValidateAssignments Resource Type=’User’
Software Metering Usage Report Cycle
CPApplet Name: Software Metering Usage Report Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000031}
Windows Installer Source List Update Cycle
CPApplet Name: MSI Product Source Update Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000032}
There are a few Scheduled Messages that do not correspond to Client Actions that can be triggered via the GUI.
Refresh default MP
ScheduledMessageID: {00000000-0000-0000-0000-00000023} LSRefreshDefaultMPTask
Refresh Location
ScheduledMessageID: {00000000-0000-0000-0000-00000024} LSRefreshLocationsTask
Timeout Location Service Requests
ScheduledMessageID: {00000000-0000-0000-0000-00000025} LSTimeOutRequestsTask
Manage Certificates
ScheduledMessageID: {00000000-0000-0000-0000-00000051} CertMaintenance
(From http://www.myitforum.com/articles/8/view.asp?id=6757)
Hardware Inventory Cycle
CPApplet Name: Hardware Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000001}
Software Inventory Cycle
CPApplet Name: Software Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000002}
Discovery Data Collection Cycle
CPApplet Name: Discovery Data Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000003}
File Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000010}
ID MIF Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000011}
Machine Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate Machine Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000021} RequestAssignments Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000022} Evaluate Policy Resource Type=’Machine’
The Machine Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context with no corresponding Client Actions.
ScheduledMessageID: {00000000-0000-0000-0000-00000040} CleanupPolicy Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000042} ValidateAssignments Resource Type=’Machine’
User Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate User Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000026} RequestAssignments Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000027} Evaluate Policy Resource Type=’User’
The User Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context.
ScheduledMessageID: {00000000-0000-0000-0000-00000041} CleanupPolicy Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000043} ValidateAssignments Resource Type=’User’
Software Metering Usage Report Cycle
CPApplet Name: Software Metering Usage Report Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000031}
Windows Installer Source List Update Cycle
CPApplet Name: MSI Product Source Update Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000032}
There are a few Scheduled Messages that do not correspond to Client Actions that can be triggered via the GUI.
Refresh default MP
ScheduledMessageID: {00000000-0000-0000-0000-00000023} LSRefreshDefaultMPTask
Refresh Location
ScheduledMessageID: {00000000-0000-0000-0000-00000024} LSRefreshLocationsTask
Timeout Location Service Requests
ScheduledMessageID: {00000000-0000-0000-0000-00000025} LSTimeOutRequestsTask
Manage Certificates
ScheduledMessageID: {00000000-0000-0000-0000-00000051} CertMaintenance
Force SCCM clients to check for new program advertisements
Q: How can I force my SCCM clients to check for new program advertisements?
A: Program advertisements occur as part of the Machine Policy Retrieval & Evaluation cycle action in the SCCM Client.
To force a client to find new programs that are available ahead of the regular discovery phase, perform these steps:
1. Start the Systems Management Control Panel applet (Start, Settings, Control Panel, Configuration Manager).
2. Click the Actions tab.
3. Select "Machine Policy Retrieval & Evaluation Cycle" and click Initiate Action.
4. Close the Systems Management Control Panel applet. Within a few minutes, the new-program advertisements should be visible. Alternatively, you can use the Policy Spy Tool to force a Machine policy retrieval. You can download the Policy Spy Tool at http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp.
Q: When you distribute sw to user collections what triggers the installation?
A: It is the "User policy retrieval and evaluation cycle" that triggers the installationThe interval of "User policy retrieval and evaluation cycle" is defined in the Computer Client Agent properties on the SCCM server:
(http://technet.microsoft.com/en-us/library/bb693764.aspx)
SCCM console -> site management-> site name XXXX -> site settings -> client agents -> right click
By default it’s 60 minutes.
A: Program advertisements occur as part of the Machine Policy Retrieval & Evaluation cycle action in the SCCM Client.
To force a client to find new programs that are available ahead of the regular discovery phase, perform these steps:
1. Start the Systems Management Control Panel applet (Start, Settings, Control Panel, Configuration Manager).
2. Click the Actions tab.
3. Select "Machine Policy Retrieval & Evaluation Cycle" and click Initiate Action.
4. Close the Systems Management Control Panel applet. Within a few minutes, the new-program advertisements should be visible. Alternatively, you can use the Policy Spy Tool to force a Machine policy retrieval. You can download the Policy Spy Tool at http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp.
Q: When you distribute sw to user collections what triggers the installation?
A: It is the "User policy retrieval and evaluation cycle" that triggers the installationThe interval of "User policy retrieval and evaluation cycle" is defined in the Computer Client Agent properties on the SCCM server:
(http://technet.microsoft.com/en-us/library/bb693764.aspx)
SCCM console -> site management-> site name XXXX -> site settings -> client agents -> right click
By default it’s 60 minutes.
Subscribe to:
Posts (Atom)
Posts
