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.

Labels:

Comments

  1. AnonymousJuly 2, 2013 at 8:54 PM

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

    ReplyDelete

Post a Comment

Popular posts from this blog

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center
Post a Comment
Read more

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.
Post a Comment
Read more