SCCM Client installation Fail error 1601.

While installating SCCM client in systems via client push and Manuall installation, facing below error.

"Installation failed with error code 1601"

by accessing ccmsetup.log on perticular client  and server i found above error,

Cause : 

This is a fatal error while installing SCCM client with Windows installer service.

Resolution :

1) open command prompt.
2) Access effected computers by using PSEXEC.
3) type command "net start msiserver"

if above command gives error or could not find specific service in computer then download windows installer service and install it.
hear is the download link : http://support.microsoft.com/kb/942288

Windows Installer 4.5 is now available as a redistributable system component for the following operating systems:

• Windows Server 2008, 32-bit editions
• Windows Server 2008, 64-bit editions
• Windows Server 2008, Itanium-based editions
• Windows Vista
• Windows Vista Service Pack 1 (SP1)
• Windows XP Service Pack 2 (SP2)
• Windows XP Service Pack 3 (SP3)
• Windows Server 2003 SP1
• Windows Server 2003 SP2

Regards,,

Gaurang Patel

Run Charts in ConfigMgr Reports when the Reporting Point is located on a Windows Server 2008 x64 server / HTTP Error 500.19 – Internal Server Error

At a customer site last week, I used Windows Server 2008 x64 to host all the ConfigMgr roles, including the Reporting point. I also installed the Microsoft Office Web Components to add chart support to some of the reports. But I kept getting this error “This report has a chart, but the Microsoft Office Web Components required to view charts are not installed on the Reporting Point. Please contact your administrator." I remember reading Some blogs about changing the whole web server in Windows Server 2003 x64 to run as a 32 bit web server. So narrowing down the problem is that the Microsoft Office Web Components is 32 bit application and the Reporting Point is running in the Default Application Pool (DefaultAppPool) on the web server, which is running 64 bit.

You might have read that in Windows Server 2008 x64 web server is it possible to run different applications in different worker processes. This means that by changing the application pool for the Reporting Point to run as a 32 bit application, is it possible run the Charts in the ConfigMgr web reports. So I did and problem solved.

After installing System Center Configuration Manager 2007 SP2 (SCCM) on a Windows Server 2008 SP x64 system, I decided to install also the Reporting Point on this Site Server.

SQL Reporting Services and ConfigMgr Report Services Point configured properly and I didn't had any issues copying and running reports on IIS 7.0. But when I came to a report that had a graph I got the following message:

"This report has a chart, but the Microsoft Office Web Components required to view charts are not installed on the Reporting Point. Please contact your administrator."

I downloaded and installed in the Office 2003 Add-in: Office Web Components from

http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76&DisplayLang=en

After that, I tried to run again the report and still I was getting the same informational message.

After doing some research on the issue I found that I need to create a custom Application Pool with enable32BitAppOnWin64 set to True. This because the worker responsible to execute the graphs needs to operate in 32bit mode. Then I've assigned the reporting point web site to the custom 32bit application pool and when I tried to open the reporting point web site on a browser I got a new error message.

HTTP Error 500.19 – Internal Server Error

So I started wondering what causes the problem. After some research again I identified that it was WSUS 3.0 SP2 x64 and more specifically the 64bit version compression module (suscomp.dll).

Therefore the solutions on this were the following. Either disable totally the compression scheme on the web site, but this will cause wsus responses to be uncompressed and this will cause some performance degradation. Or to replace the 64bit version of suscomp.dll with the 32bit version.

To view the compression scheme, run the following command

%windir%\system32\inetsrv\appcmd.exe list config -section:system.webServer/httpCompression

the command will display the compression scheme for the webserver. Schemes are registered globally therefore by removing them, the compression is disabled on the webserver.

To remove the compression scheme type:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

To add the compression scheme type:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']

References

Run Charts in ConfigMgr Reports when the Reporting Point is located on a Windows Server 2008 x64 serverhttp://uje.spaces.live.com/blog/cns!DAE27042D25E8A2A!310.entry

500.19 Error When Enabling 32-bit Application Poolhttp://forums.iis.net/t/1149768.aspx

Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.19 – Internal Server Error"http://support.microsoft.com/kb/942055

HOWTO Install Exchange 2010 - Step by Step

Install the Windows Server 2008 R2 operating system prerequisites

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack

  

http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en

1. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

2. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

Restart

3. After the system has restarted, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:

Set-Service NetTcpPortSharing -StartupType Automatic

Prepare Active Directory

http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx

Prerequisites

• Your domains and the domain controllers must meet the system requirements in the "Network and Directory Servers" section of Exchange 2010 System Requirements.
• In each domain in which you will install Exchange 2010, you must have at least one domain controller running Windows Server 2003 Service Pack 1 (SP1).
• If you are running the release to manufacturing (RTM) version of Exchange 2010 Setup.com, in each domain (including child domains) where you have the Exchange Enterprise Servers and Exchange Domains Servers security groups and therefore must run Setup /PrepareLegacyExchangePermissions, you must have at least one domain controller running Windows Server 2003 SP1 or a later version.
• If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domains by using a computer running Windows Server 2008, you must first install the Active Directory management tools on the Windows Server 2008 computer prior to preparing the schema or domains. To do this, run the following command.

ServerManagerCmd -i RSAT-ADDS

• The computers on which you will install Exchange 2010 must meet the system requirements. For details, see Exchange 2010 System Requirements.

Prepare Active Directory and domains

1.        If you have any computers in your organization running Exchange 2003, open a Command Prompt window, and then run one of the following commands:

o    To prepare legacy Exchange permissions in every domain in the forest that contains the Exchange Enterprise Servers and Exchange Domain Servers groups, run the following command.
setup /PrepareLegacyExchangePermissions.or setup /pl

o    To prepare legacy Exchange permissions in a specific domain, run the following command.
setup /PrepareLegacyExchangePermissions: < FQDN of domain you want to prepare > or setup /pl:<FQDN of domain you want to prepare>

Note:

You can skip this step and prepare the legacy Exchange permissions as part of Step 2 or Step 3. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

1.        Note the following:

o    To run this command to prepare every domain in the forest, you must be a member of the Enterprise Admins group. To run this command to prepare a specific domain, or if the forest has only one domain, you must be delegated the Exchange Organization Management role, and you must be a member of the Domain Admins group in the domain that you will prepare.

o    If you don't specify a domain, the domain in which you run this command must be able to contact all domains in the forest. If the server can't contact a domain that must have legacy Exchange permissions prepared, it prepares the domains that it can contact, and then returns an error message that it was unable to contact some domains.

o    You can run this command from any 64-bit Windows Server 2003 SP1 server in the forest.

o    You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency. For information on how to identify the schema master, see Identify the schema master. To change site membership for the schema master:

5. For information on how to transfer

o After you run this command, you must wait for the permissions to replicate across your Exchange organization before continuing to the next step. If the permissions haven't replicated, the Recipient Update Service on your Exchange Server 2003 computers could fail. The amount of time that replication takes depends on your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Microsoft Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

1.        For detailed information about the permissions set by this command, see Preparing Legacy Exchange Permissions.

From a Command Prompt window, run the following command.
setup /PrepareSchema or setup /ps

Note:

You can skip this step and prepare the schema as part of Step 3.

Important:

You must not run this command in a forest in which you don't plan to run setup /PrepareAD. If you do, the forest will be configured incorrectly, and you won't be able to read some attributes on user objects.

Note:

It isn't supported to use the LDIF Directory Exchange tool (LDIFDE) to manually import the Exchange 2010 schema changes. You must use Setup to update the schema.

This command performs the following tasks:

o Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2010 specific attributes. The LDIF files are copied to the Temp directory, and then deleted after they are imported into the schema.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step.

Note the following:

o If you want to verify the updates to the schema before the changes are replicated to other servers in the domain, you must disable outbound replication on the computer on which you run the command before you run it, and then enable outbound replication after you have verified that the import completed successfully.

o To run this command, you must be a member of the Schema Admins group and the Enterprise Admins group.

o You must run this command on a 64-bit computer in the same domain and in the same Active Directory site as the schema master.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o If you use the /DomainController parameter with this command, you must specify the domain controller that is the schema master.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

For more information, see Exchange Server Changes to the Active Directory Schema.

From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName: <organization name> ] or setup /p [/on:<organization name>]
This command performs the following tasks:

o If the Microsoft Exchange container doesn't exist, this command creates it under CN=Services,CN=Configuration,DC=<root domain>.

o If no Exchange organization container exists under CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain >, you must specify an organization name by using the /OrganizationName parameter. The organization container will be created with the name that you specify.
The Exchange organization name can contain only the following characters:
A through Z
a through z
0 through 9
Space (not leading or trailing)
Hyphen or dash
The organization name can't contain more than 64 characters. The organization name can't be blank. If the organization name contains spaces, you must enclose the name in quotation marks.

o Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<your organization>, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container. The objectVersion value for the RTM version of Exchange Server 2007 is 10666.

o If they don't exist, creates the following containers and objects under CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>. These are required for Exchange 2010.
CN=Address Lists Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Addressing,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Client Access,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Connections,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Folders Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Global Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Mobile Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Recipient Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=System Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM AutoAttendant,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM DialPlan,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM IPGateway Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>

o If it doesn't exist, creates the default Accepted Domains entry, based on the forest root namespace, under CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

o Assigns specific permissions throughout the configuration partition.

o Imports the Rights.ldf file. This adds the extended rights required for Exchange to install into Active Directory.

o Creates the Microsoft Exchange Security Groups organizational unit (OU) in the root domain of the forest and assigns specific permissions on this OU.

o Creates the following universal security groups (USGs) within the Microsoft Exchange Security Groups OU:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange Servers
Exchange View-Only Administrators
Exchange Public Folder Administrators (New in Exchange Server 2007 Service Pack 1)
ExchangeLegacyInterop

o Adds the new USGs that are within the Microsoft Exchange Security Groups OU to the otherWellKnownObjects attribute stored on the CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> container.

o Creates the Unified Messaging Voice Originator contact in the Microsoft Exchange System Objects container of the root domain.

o Prepares the local domain for Exchange 2010. For information about what tasks are completed to prepare a domain, see Step 4.

Note the following:

o To run this command, you must be a member of the Enterprise Admins group.

o The computer where you run this command must be able to contact all domains in the forest on port 389.

o You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency.

o If you haven't completed Step 1, setup /PrepareAD will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. If you are also a member of the Schema Admins group, and if you haven't completed Step 2, setup /PrepareAD will automatically perform the PrepareSchema step. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology. 

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it is located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

o To verify that this step completed successfully, make sure that there is a new OU in the root domain called Microsoft Exchange Security Groups. This OU should contain the following new Exchange USGs:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange View-Only Administrators
Exchange Servers
Exchange Public Folder Administrators (new in Exchange 2007 SP 1)
ExchangeLegacyInterop

From a Command Prompt window, run one of the following commands:

o Run setup /PrepareDomain or setup /pd to prepare the local domain. Note that you don't need to run this in the domain where you ran Step 3. Running setup /PrepareAD prepares the local domain.

o Run setup /PrepareDomain:<FQDN of domain you want to prepare> to prepare a specific domain.

o Run setup /PrepareAllDomains or setup /pad to prepare all domains in your organization.

These commands perform the following tasks:

o Sets permissions on the domain container for the Exchange Servers, Exchange Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators.

o If this is a new organization, creates the Microsoft Exchange System Objects container in the root domain partition in Active Directory and sets permissions on this container for the Exchange Servers, Exchange Organization Administrators, and Authenticated Users. This container is used to store public folder proxy objects and Exchange-related system objects, such as the mailbox database's mailbox.

o Sets the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain>. This objectVersion property contains the version of domain preparation. The version for Exchange 2007 RTM is 10628.

o Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain.

Note:

The Exchange Install Domain Servers group is used if you install Exchange 2010 in a child domain that is an Active Directory site other than the root domain. The creation of this group allows you to avoid installation errors if group memberships haven't replicated to the child domain.

o Assigns permissions at the domain level for the Exchange Servers USG and the Exchange Recipient Administrators USG.

Note the following:

o For domains that are in an Active Directory site other than the root domain, /PrepareDomain might fail with the following messages:
"PrepareDomain for domain <YourDomain> has partially completed. Because of the Active Directory site configuration, you must wait at least 15 minutes for replication to occur, and run PrepareDomain for <YourDomain> again."
"Active Directory operation failed on <YourServer>. This error is not retriable. Additional information: The specified group type is invalid.
Active Directory response: 00002141: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0
The server cannot handle directory requests."
If you see these messages, wait for or force Active Directory replication between this domain and the root domain, and then run /PrepareDomain again.

o To run setup /PrepareAllDomains, you must be a member of the Enterprise Admins group.

o To run setup /PrepareDomain, if the domain that you are preparing existed before you ran setup /PrepareAD, you must be a member of the Domain Admins group in the domain. If the domain that you are preparing was created after you ran setup /PrepareAD, you must be a member of the Exchange Organization Administrators group, and you must be a member of the Domain Admins group in the domain.

o You must run this command in every domain in which you will install Exchange 2007. You must also run this command in every domain that will contain mail-enabled users, even if the domain doesn't have Exchange 2007 installed.

To verify that this step completed successfully, confirm the following:

o You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers.

Note:

To view the Microsoft Exchange System Objects container in Active Directory Users and Computers, on the View menu, click Advanced Features.

o The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.

o On each domain controller in a domain in which you will install Exchange 2010, the Exchange Servers USG has permissions on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.

Install Exchange Server 2010

How to Create Drop Down Menu in Excel

Solution

1.     Open Microsoft Excel.

2.     Enter numbers in A1:A10 as the list source. These numbers will appear in the drop-down list. Select the cell (here is E5) that will contain the drop-down list. Choose Date-> Date tools-> Date Validation to access the Data Validation dialog box.

Enter source and access the dialog box.

Data Validation dialog box

3.     In the Settings tab, select the List option in Allow drop-downlist. Make sure that the In-Cell Dropdown check box is checked.

Select the list option.

4.     Then, click here . The following dialog box will appear.

date validation box

5.     Select the items that will appear in the dropdown list from the worksheet using your mouse , click and return to theData Validation dialog box, click OK.

6.     Then, a drop-down list is created .

A drop-down list is created.

Tips

• If your list is short, you can enter the items directly into the Source control in the Settings tab of the Data Validation dialog box. And separate each item with list separators specified in your regional settings.
• If your list is in a range on a different worksheet, you can provide a name for the range and then use the name as your list source (preceded by an equal sign). For example, if the list is on a different sheet in a range named List, enter the following: "=List".

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter