Provisioning your UCMA applications-choosing the right location

Unfortunately, this post has more questions than answers, but hopefully it can try to explain how to get around a nasty error I’ve run into with UCMA. First, if you’re not familiar with creating app GRUUs with ApplicationProvisioner.exe, check out the MSDN article first-it’s got some good step by step instructions, and should cover you for most scenarios.

The situation I ran into may be a little more esoteric, but the application that was being provisioned needed to sit in the DMZ. When going through which servers had capacity, the first candidate that our IT group identified was the machine that was also running the OCS Edge server. I had a strange feeling at the time that this wouldn’t work, and sure enough, the following error popped up when I tried to create the GRUU:

Checking on the front end server, you won’t see the edge server in the list of trusted hosts, but based on the error message, it might imply that the edge server is automatically treated as authenticated, since the app name and port were definitely unique.  What’s strange is that trying to provision the same application on another server that is actually listed as a trusted host works…or at least the provisioner will create a GRUU for it.  When you try to run an app on that server though, the app will fail when setting up an ApplicationEndpoint.  The same thing happens if the FQDN of an already provisioned application is added as a trusted host-you can add the trusted host entry, but the application will stop working. 

I suppose there are a couple of takeaways from this exercise.  First, even though you don’t get an explicit error from provisioning, don’t try running a UCMA application on a trusted host, at least when “treat as authenticated” is checked.  This should be pretty straightforward, since with Application users in R2, there aren’t a whole lot of cases where you’d need to create trusted host entries anymore.  The second takeaway though is that running a UCMA application on the edge server is apparently not supported, and the error that you get isn’t really an intuitive one. 

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s