SUPPORT Q&A - SDNS TOOL

Phil - Friday, February 12, 2010 4:32 PM:

Is there any way around having to use the SDNS tool or manually pushing the .NET configuration change?

I'm thinking there is not, but any ideas would be greatly appreciated. I am trying to push Aras out within a project of about 100 people and this is becoming a big sticking point.

Essentially, the problem is the end-users (clients) do not have administrative rights on their pc's.  So they are not able to use the tool themselves.  The IT team refuses to push out the configuration change, and the whole thing is becoming quite the mess. 

Again, any input on this would be greatly appreciated.

Bill - Friday, February 12, 2010 5:01 PM:

sdns.exe was designed as an alternative for single PC setup only.  It wasn't designed for use in deployment.

 Section 4 "IT System Administrator Push Configuration" of the Aras Innovator 9.1 - .NET Client Configuration document outlines how to create a .NET security policy for use in deployment.

http://www.aras.com/support/documentation/9.1.0/Installation%20and%20Configuration/Aras%20Innovator%209.1%20-%20.NET%20Client%20Configuration.pdf

Microsoft provides documentation on how to convert the .NET Security Policy into an MSI that can be pushed out to users over Active Directory, as well as discussing some alternate methods of central deployment.

http://msdn.microsoft.com/en-us/library/aa302354.aspx

Hope it helps.

-Bill

Phil - Friday, February 12, 2010 5:09 PM:

I did see that in the install guide...my issue is that the IT group (which oddly enough I am not a part of), is very reluctant to push the setting for me. I was just wondering if there was any possible work-around out there that could be implemented to avoid having to change this policy.

I am still somewhat confused as to why the policy has to be changed? Is it due to the Active X components?

Bill - Friday, February 12, 2010 5:30 PM:

Not sure I can help you get around the IT depatment on this one.  You need admin rights to set .NET Security Policies.  Creating the MSI might make it simpler for you though.

The default policies will not allow the .NET libraries(not activex) to be evaluated on the client.  You are setting a policy that allows them to loaded.

-Bill