Terminal server gateway error XP Sp3

Het kan voorkomen dat je onderstaande melding krijgt:
 "This computer can't connect to the remote computer because the Terminal Services Gateway server address is unreachable or incorrect. Type a valid server address"

oplossing is het installeren van onderstaande KB:
http://support.microsoft.com/kb/951607

Default gateway verdwijnt na reboot

Command prompt: netsh int ip reset

Exchange 2010 remote mailbox move error after SP2 update

Men kreeg onderstaande fout met mailbox move van de cloud naar on-premise

 

Door de SP2 update van Exchange is de mrsproxy weer disabled, deze is nodig voor een remote mailbox move van en naar de cloud.

 

onderstaand commando dient uitgevoerd te worden op de CAS server:

Set-WebServicesVirtualDirectory -Identity “server\EWS(default Web site)” –MRSProxyEnabled $true

 

Bron: http://community.office365.com/en-us/wikis/exchange/remote-mailbox-moves-fail-after-installing-exchange-2010-sp2.aspx

 

TMG RDP issue inloggen (duurt lang)

Soms duurt het inloggen op een TMG server lang, dit heeft te maken met het feit dat een TMG server meestal 2 netwerk interfaces heeft waardoor RDP de weg niet goed weet dit kun je oplossen door onderstaande uit te voeren:

RDP-TCP veranderen van alle network adapters naar de internal adapter, nu zat de DMZ er ook tussen waardoor je vreemde zaken krijgt met een rdp sessie

http owa redirect to https error

Je kunt op de CAS server van exchange binnen IIS een http redirect zetten naar de https owa website, echter krijg je dan onderstaande fout:

 

Om dit op te lossen ga je als volgt te werk:

 

Maak de redirect aan op de default website:

 

Zet Require SSL uit op de defautl website.

 

doe een eventuele IIS reset

 

Bron: http://technet.microsoft.com/en-us/library/aa998359.aspx

 

 

 

Flash update definitief uitschakelen

update process

Administrators can configure auto-update notification settings by deploying a file named mms.cfg. The mms.cfg file is intended for configuration by an IT administrator and is stored on the user's computer. Flash Player installation does not create the file. You can use third-party administration tools, such as Microsoft System Management Server, to replicate the configuration file to the user's desktop.

The mms.cfg file is a UTF-8 text file. The format of the mms.cfg file is a series of name=value pairs separated by carriage returns. If a parameter is not set in the file, Flash Player assumes the default value. When set, values in this file override the user-configured settings stored in a per-user local shared object.

Note: Settings in mms.cfg override the users settings and users cannot change it through Settings Manager. Settings Manager, as viewed by the user, doesn't reflect configuration settings set by mms.cfg.

If you are deploying Flash Player 8 or later, store the mms.cfg file in the following location depending on the operating system:

·         Windows NT, 2000-- C:\WINNT\System32\Macromed\Flash

·         Windows XP, Vista --C:\WINDOWS\System32\Macromed\Flash

·         Windows 95, 98, or ME--C:\Windows\System\Macromed\Flash

·         Windows 64 bit -- C:\Windows\SysWOW64

·         Macintosh--\Application Support\Macromedia

For player versions earlier than Flash Player 8, store the mms.cfg file in the following location depending on the operating system:

·         Windows NT, 2000--C:\WINNT\System32

·         Windows XP, Vista-- C:\WINDOWS\System32

·         Windows 95, 98, or ME--C:\Windows\System

·         Windows 64 bit -- C:\Windows\SysWOW64

·         Macintosh-- \Application Support\Macromedia

Note: Flash Player 8 and later versions can read mms.cfg from either the new or old location. If mms.cfg exists in both locations, Flash Player 8 reads settings from the new location.

The following table describes settings in the mms.cfg file:

Parameter	Default	Description
AutoUpdateDisable	0	0 allows auto-update based on user settings. 1 disables auto-update.
AutoUpdateInterval	<0 (or absent)	Takes a numeric value. <0 (or absent) uses value from player settings. 0 checks for updates every time the player launches. >0 specifies the minimum number of days between check for updates.
SilentAutoUpdateEnable	1	0 allows background update. 1 disables background update.

Disable auto-update notification

1.     Create or open the mms.cfg file in a text editor.

2.     Add the following auto-update setting:
AutoUpdateDisable=1

3.     Save the mms.cfg file with UTF-8 encoding in the correct system location for the user's operating system.

4.     Close and restart Flash Player or the browser in which Flash Player is running for the new setting to take effect.

Enable background update process

1.     Create or open the mms.cfg file in a text editor.

2.     Add the following auto-update setting:
AutoUpdateDisable=0
SilentAutoUpdateEnable=1

3.     Save the mms.cfg file with UTF-8 encoding in the correct system location for the user's operating system.

4.     Close and restart Flash Player or the browser in which Flash Player is running for the new setting to take effect.

Test auto-update notification settings

Administrators can verify the mms.cfg configuration has disabled auto-update by using a packet sniffer with the following test:

1.     In mms.cfg, set AutoUpdateDisable=0 to allow auto-update. Verify that auto-update is enabled in Settings Manager.

2.     Add the auto-update setting:
AutoUpdateInterval=0
With this setting, Flash Player requests the version file every time it starts and the request appears in the network request traffic.

3.     Open a web page with Flash content to start Flash Player. A simple page with a single piece of Flash content is best, to minimize the network traffic in the packet sniffer log. The packet sniffer shows the auto-update request traffic to http://fpdownload.macromedia.com/
Note: Avoid using www.macromedia.com as your test page, since the auto-update request is lost in the other file requests.

4.     Set the AutoUpdateDisable to 1 to disable auto-update notification.

5.     Open a web page with Flash content to start Flash Player. There is no version file request traffic.

Bron: http://helpx.adobe.com/flash-player/kb/administration-configure-auto-update-notification.html

Office 365 ADFS trust

Gebruikers krijgen onderstaande fout te zien, dat men niet aangemeld kan worden bij de organisatie.

 

Het certificaat tussen de ADFS server en Office 365 bleek te zijn verlopen, dit is met onderstaande powershell commando's opgelost.

1 voor 1 zijn onderstaande regels uitgevoerd op de ADFS server.

$cred = Get-Credential

Set-ExecutionPolicy unrestricted

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection

Import-PSSession $session

Connect-MsolService -Credential:$cred

Set-MsolADFSContext -Computer:<computername adfs server>

Update-MsolFederatedDomain -DomainName:korein.nl -SupportMultipleDomain

Dit is een jaarlijks terugkerend  iets! dus zorg ervoor dat je een agenda afspraak noteert!!!