Submitted by inder on Thu, 06/17/2010 - 06:43
Submitted by inder on Thu, 06/17/2010 - 06:46
nAppliance nUAG remote access appliance platform is a next generation, high-performance application access and security solution which unifies a Web application firewall, SSL VPN, endpoint security to enable secure application access, access control and content inspection for a wide variety of line-of-business applications.
Submitted by inder on Thu, 06/17/2010 - 06:54
When publishing SharePoint portal through the Microsoft UAG Server it removes the default “Sign Out” link on the SharePoint portal which is otherwise visible when accessing internally (Corporate network without going through UAG). Some people do think this as an issue but really this isn’t an issue rather a feature of UAG.
Submitted by inder on Thu, 06/17/2010 - 06:59
On few occassions you may encounter an issue wherein the nUAG appliance when started and joined to the domain for the first time will take long time to start and when it starts the MS Firewall service stays in "starting" state. This problem occurs mostly when user has not followed the quick start guide properly and continued with the steps one after the other. Two ways to resolve it;
Submitted by inder on Thu, 06/17/2010 - 07:04
By default, computers running Windows Vista and Windows XP operating systems cannot access RemoteApps and Remote Desktops published through Forefront Unified Access Gateway (UAG) 2010. However, by applying Update 1 for Microsoft UAG you can access these applications from Windows XP SP3, Windows Vista with Service Pack 1 and Windows Vista with Service Pack 2. What we found out from our initial research was that even with UP1 Windows XP SP3 machines will not be able to access these applications.
Submitted by inder on Thu, 06/17/2010 - 07:14
We will discuss various scenarios related to accessing Citrix Presentation Server (Web Interface 3.0/4.0/4.5) and Citrix XenApp (Web Interface 5.0) from Mac OS 10 X machines which are published through UAG and IAG SP2 UP3(In general IAG SP2), but not configuration.
Submitted by inder on Tue, 07/06/2010 - 03:23
This is a very common situation which people might face when deploying Microsoft DirectAccess technology. Before going into how to work around this we need to know why the applications which work in internal network would fail to work on DirectAccess connectivity.
Let’s go through few types of applications and the reasons why they might fail to connect
Client/Server Applications
Submitted by inder on Thu, 07/08/2010 - 08:22
Submitted by inder on Wed, 07/21/2010 - 12:39
Supported client OS: Windows XP 32bit and Windows Vista 32bit
Submitted by inder on Wed, 07/21/2010 - 12:59
While working on a support case recently, i came across this issue wherein we were trying to publish an application and there was a warning message generated in the web monitor logs about "POST without Content-Type not Allowed" while accessing it from a client machine.
Pages
