terran
Posts: 6
Joined: 8.Sep.2010
Status: offline
|
I've posted this in our Microsoft Partner forums but the engineer said UAG is currently not supported there so I hope someone else might be able to help here: I've been running into an issue while generating the policies at the end of configuring UAG. It appears to be a certificate issue and I've tried changing the: "Browse and select a root or intermediate certificate that verifies certificates sent by DirectAccess clients." to: 1. Use root certificate 2. Use intermediate certificate but both throw an error while generating the policies with the following error: > Executing policy script. Unexpected token 'The' in expression or statement. At C:\Users\tluk\AppData\Local\Temp\tmpFE62.tmp.ps1:13 char:80 + if (-not ${UAGDA_CERT_MACHINE_AUTH}) { ${UAGDA_CERT_MACHINE_AUTH}="C=US, O="T he <<<< Go Daddy Group, Inc.", OU=Go Daddy Class 2 Certification Authority" } + CategoryInfo : ParserError: (The:String) [], ParseException + FullyQualifiedErrorId : UnexpectedToken @ > aborted It almost looks like there's a parsing issue caused by the name of the go daddy certificate so I exported and opened the script: # UAGDA Group Policy Configuration Script. # Generated on Tuesday, 07 September 2010 18:43 UTC. # Generator Version 4.0.0.0 # Runtime variables Param( [parameter(Mandatory=$False, ValueFromPipeline=$true, HelpMessage="A domain controller, in domain.com for faster operations.")][String] $DomainControllerComputerName, [parameter(Mandatory=$False, ValueFromPipeline=$true, HelpMessage="Additional domains(seperated by '|') to link the app-server's policy to.")][String] $AdditionalAppServerDomains, [parameter(Mandatory=$False, ValueFromPipeline=$true, HelpMessage="Additional domains(seperated by '|') to link the client's policy to.")][String] $AdditionalClientDomains ) # Static variables if (-not ${UAGDA_ACCESS_ENABLING_ADDRESSES_ALL}) { ${UAGDA_ACCESS_ENABLING_ADDRESSES_ALL}="2002:480e:ae7c:8001::ac14:105,2002:480e:ae7c:8000:0:5efe:172.20.1.5,2002:480e:ae7c:8001::ac14:10a,2002:480e:ae7c:8000:0:5efe:172.20.1.10,2002:480e:ae7c:8001::ac14:108,2002:480e:ae7c:8000:0:5efe:172.20.1.8,2002:480e:ae7c:8001::ac14:172,2002:480e:ae7c:8000:0:5efe:172.20.1.114,2002:480e:ae7d::480e:ae7d" } if (-not ${UAGDA_CERT_MACHINE_AUTH}) { ${UAGDA_CERT_MACHINE_AUTH}="C=US, O="The Go Daddy Group, Inc.", OU=Go Daddy Class 2 Certification Authority" } if (-not ${UAGDA_CERT_TYPE}) { ${UAGDA_CERT_TYPE}="root" } Does this have anything with the extra quotes: O="The Go Daddy Group, Inc." It looks like the extra quotes terminated the parsing of the string too early. Here's what is displayed before we hit the "Apply now" button: The root certificate to which remote clients chain is: C=US, O="The Go Daddy Group, Inc.", OU=Go Daddy Class 2 Certification Authority The certificate that the DirectAccess server uses for HTTPS is: CN=portal1.domain.com, OU=Domain Control Validated, O=portal1.domain.com I made the change in the script to take out the extra quotes then executed it from command shell and while it did run, it failed at: Executing Set UAG DirectAccess Client - Clients Access Enabling Tunnel - All. ... failed. CA name not specified Usage: add rule name=<string> endpoint1=any|localsubnet|dns|dhcp|wins|defaultgatew ay| <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list> endpoint2=any|localsubnet|dns|dhcp|wins|default gateway| <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list> action=requireinrequestout|requestinreques tout| requireinrequireout|requireinclearout|noauthentication [description=<string>] [mode=transport -------------------------------- Has anyone experienced a similar issue?
|