These changes need to be done on your Remote Desktop Web Access server. Always backup files that you intend to edit and be aware that Windows updates and service packs can override your changes. To change the default page header “Remote Desktop Services Default Connection” edit C:\Windows\Web\RDWeb\App_Data\RDWebAccess.ConfigLine 20.

Issue Browsing to Remote Desktop Web Access site (RemoteApp Programs page) Internet Explorer 11 users are greeted with warning message: Browser Not SupportedThis Web browser is not supported by RD Web Access. RD Web Access requires Internet Explorer 6.0 or later.Vou can download the latest version of Internet Explorer from the Windows Update Web site.

Background Windows Server 2008 R2 Domain Windows Server 2008 R2 Remote Desktop Server with following roles: Remote Desktop Session Host Remote Desktop Licensing (User CALs) Remote Desktop Web Access Issue Every time non-administrator user logs on via Remote Desktop connection, following Warning is logged in System Logs:

Even if your external Exchange Autodiscover service is configured correctly you may still have issues with rejected login credentials if your internal and SMTP domains are different. Lets say your internal Active Directory domain is mydomain.local, but your external SMTP domain is mydomain.com and user’s have emails in format name@mydomain.com. In this case Autodiscover service…

Background This article assumes that your Exchange Autodiscover is setup and working correctly internally. For external connections MS Exchange Autodiscover uses following 4 methods to retrieve automatic email client configuration: Connecting to Autodiscover URL: https://domain.com/AutoDiscover/AutoDiscover.xml Connecting to Autodiscover URL: https://autodiscover.domain.com/AutoDiscover/AutoDiscover.xml Connecting to Autodiscover redirect URL and looking for Redirection to HTTPS Autodiscover at: http://autodiscover.domain.com/autodiscover/autodiscover.xml Looking…

Error while installing Mozy Pro Client on Windows Server 2008 R2 – “mozyproshell.dll failed to register“. Issue was resolved by installing Microsoft Visual C++ 2008 Redistribute. 32 bit version can be downloaded from here, 64 bit – from here. Source. Windows Server 2008 R2Mozy Pro 2.26.0.376

Following error was displayed while checking DFS replication backup on Windows Server 2012: [ERROR] Failed to execute GetVersionVector method. Err: -2147217406 (0x80041002) The issue was caused by a recent unexpected DFS server shutdown. Windows Server 2008 R2 and Windows Server 2012 by default do not automatically resume DFS replication after dirty DFSR JET database shutdown.…

If DFS on Windows Server 2008R2 and Windows Server 2012 detects dirty DFSR JET database shutdown it pauses replication and records following warnings is DFS Application logs: Source: DFSREvent ID: 2213Description:The DFS Replication service stopped replication on volume D:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled.…

To return My Computer icon to Windows Desktop on Windows Server 2012: In the Start Screen find and open Turn Windows features on or off In Add Roles and Features Wizard, in Features section select Desktop Experience (under User Interfaces and Infrastructure)

To check DFSR backlog, run following commands on one of your DFRS servers. dfsrdiag backlog /rgname:<REPLICATION_GROUP_NAME> /rfname:<REPLICATED_FOLDER_NAME> /smem:<SERVER_1> /rmem:<SERVER_2> dfsrdiag backlog /rgname:<REPLICATION_GROUP_NAME> /rfname:<REPLICATED_FOLDER_NAME> /smem:<SERVER_2> /rmem:<SERVER_1> For verbose output, add /v switch at the very end of commands.

On the DFSR server open Command Prompt as Administrator Run WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderconfig get replicatedfolderguid,replicatedfoldernameCopy GUID of the folder you want to clean Run WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where “replicatedfolderguid='<Folder GUID>’” call cleanupconflictdirectoryReplacing <Folder GUID> with the ID you copied in the previous step

Update 2017 There is no need to mess with PowerShell commands anymore. You can set passwords to never expire in Office 365 admin GUI: Settings > Security & Privacy > Password Policy > Edit > Set user password to never expire.     Original Article To set user password to never expire on Microsoft Exchange…