Skip to main content

Cluster TEMP path on server MBXSERVER is set to the default location. For optimum performance, this path should point to a fast disk. Current TEMP path: %USERPROFILE%\AppData\Local\Temp – issue on Windows 2008 R2 and Exchange 2010 SP2


Exchange Best Practices Analyzer informs you about this issue and when you click the link offered it gets you to this web page: http://technet.microsoft.com/en-us/library/aa998044(v=exchg.80).aspx
There, the text offers you a solution to log in to a system as cluster user account.
  1. Log on to a node in the cluster as the Cluster service account.
  2. Right-click My Computer and select Properties.
  3. Select Advanced.
  4. Click Environment Variables.
  5. In the User variables for <account name> area, select TEMP and click Edit.
  6. In the Variable value field, enter the new path for the TEMP environment variable and click OK.
  7. In the User variables for <account name> area, select TMP and click Edit.
  8. In the Variable value field, enter the new path for the TMP environment variable and click OK.
  9. Click OK to close the Environment Variables dialog box and OK once more to close the System Properties dialog box.
  10. Restart the node to apply the change.
  11. Repeat steps 1 through 10 for each node in the cluster.
!!! BUT !!! In Windows 2008 R2 (I did not check other versions of Windows 2008) cluster service runs as Local System and therefore this solution is not actually a solution. On web page http://support.microsoft.com/kb/243330 you can find known security identifiers which shows that Local system’s SID is:
SID: S-1-5-18Name: Local System
Description: A service account that is used by the operating system.
Now, open the registry and go to HKEY_USERS, expand S-1-5-18/Environment and change the TEMP and TMP values with the values you want.

Comments

  1. Thanks, dude. Was bangin my head a little. Appreciate the tip.

    ReplyDelete

Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.