|
|||||
|
By Pritesh Patel, on October 7, 2011, 9:00:54 Hi, I’ve had a few occasions where a client has asked if they could have OWA or another application configured so that it can be reach directly. Sometimes they have done this themselves, and mostly they have had to ask why when a user navigates to the FQDN of the application does it not redirect to the correct path? By Pritesh Patel, on October 6, 2011, 9:00:21 Hi, What a difference a letter makes!! Whilst working on another client install, during testing we saw errors in UAG’s web monitor. The error was that a URL was not being recognised and was hitting the default rule. It happened when the user opened a new email in OWA through UAG and then clicked the address book icon. Continue reading UAG, OWA Address Book and owasl.xap error (KB 2444842). By Pritesh Patel, on September 19, 2011, 9:00:47 Hi, When trying to get a client’s UAG portals looking the same across devices mentioned in the title and desktops I found that the portal has a “slim” view when visited on Windows 7 and iPhones. Weird because the portal looks the same on an iPad. Continue reading UAG Portals, iPhones, Androids and Windows 7 phones By Pritesh Patel, on September 15, 2011, 9:00:17 Hi, Been busy and came across this during a deployment which I thought would be useful to share. If you use one of the fantastic appliances from Celestix to deploy UAG you’ll have Intel 82574L NICs installed, which support teaming. By Pritesh Patel, on August 7, 2011, 13:33:15 I came across this post somewhere on the web – still trying to get back to it so I can link back here. The interface identifier is not created according to RFC 4941, meaning there are potential issues lurking in an IPv6 deployment with Win7 machines and network hardware. Run the following command to fix: netsh interface ipv6 set global randomizeidentifiers=disabled |
|||||
|
|
|||||
