Whenever you mess up with authentication methods on the IIS or through powershell, services may not function properly, especially the published ones. Blew is the default authentication methods published at Exchange Team Blog site:

Exchange Server 2010 with the Client Access Server (standalone):

Location	Authentication	SSL Setting	Management
Default Web Site	Anonymous	Required	IIS Management Console
aspnet_client	Anonymous	Required	IIS Management Console
Autodiscover	Anonymous / Basic / Windows Authentication	Required	Exchange Management Shell
ECP	Anonymous / Basic	Required	Exchange Management Console or Shell
EWS	Anonymous / Windows Authentication	Required	Exchange Management Shell
Microsoft-Server-ActiveSync	Basic	Required	Exchange Management Console or Shell
OWA	Basic	Required	Exchange Management Console or Shell
Powershell	Anonymous	Not Required	Exchange Management Shell
RPC	Basic / Windows Authentication	Required	Exchange Management Shell
RpcWithCert	all options Disabled	Required (128 bit not checked)	N/A
OAB	Windows Authentication	Not Required	Exchange Management Console or Shell

Exchange Server 2010 Mailbox role (standalone):

Location	Authentication	SSL Setting	Management
Default Web Site	Anonymous	Required	IIS Management Console
PowerShell	Anonymous	Not Required	Exchange Management Shell

CMDlet list for those that can only be modified in the Management Shell:

Set-AutoDiscoverVirtualDirectory

Set-WebServicesVirtualDirectory

Set-PowershellVirtualDirectory

Set-OutlookAnywhere (for the RPC virtual directory)

Hello ,

I’ve been (and I think most of you did) through the WSUS configuration and waiting for days for the download to finish.

That’s because the the BITS technologies that limits that foreground download, and enable the background downloads – to least impact the bandwidth.

We used to use this command in WSUS 2.0

WsusDebugTool.exe /tool:setforegrounddownload

But in WSUS 3.0 it’s not applicable, and if you tried to execute it, it will get you with the below error

Running... SetForegroundDownload

Error processing node: SetForegroundDownload

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

  at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SoftwareDistribution.Tools.SqlHandler.HandleQuery(TextWriter dataWriter, String baseDirectory, ArrayList sqlQueryList)

   at Microsoft.SoftwareDistribution.Tools.SqlHandler.DumpData(String baseDirectory, String nodeName, XmlNode infoXml)

   at Microsoft.SoftwareDistribution.Tools.SusServerTool.ProcessDumpNode(XmlNode dumpNode)

In WSUS 3.0, in able to speed up the downloads (foreground mode), you need to run this command

"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

To revert it back to normal, you can run the same command again and change the value to 0

"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=0"

Once you done that, you need to reset the update services service.

To install TMG, then SP1 then RU1 for any reason, is a long way drive if you follow the normal process!

I found the below way to install the slipstreamed source of TMG with SP1 in one DVD. Follow the steps as shown below to end up with the upgraded copy

1. Run the following from an elevated command prompt:

ServerManagerCmd.exe -inputpath ^<DVD_path^>\FPC\PreRequisiteInstallerFiles\WinRolesInstallSA_Win7.xml -logPath C:\Windows\TEMP\TMG-Prerequisites.log

1. Prepare a Forefront TMG SP1 slipstream DVD with the following steps:
   1. Copy the Forefront TMG DVD and the Forefront TMG SP1 MSP file to a local drive on the target computer. For the purposes of this example, let’s assume this is c:\temp\TMG.
   2. At a command prompt, type the following command and press ENTER.
      msiexec /a c:\temp\TMG\FPC\MS_FPC_SERVER.msi /p TMG-KB981324-amd64-ENU.msp /qb /L*v c:\tmg\log.txt
      When the operation completes, you will have a full installation of Forefront TMG already upgraded to Service Pack 1.

Enjoy.