Register Login 
 
 

Please use the links on the top right of the page to register and log onto SmartAccessCentral in order to post in the forums.

epa factory complete banner.gif

Subject: Rename server bug.
Forums Search
You are not authorized to post a reply.
Author
  Messages Sort:
stucco

New Member
New Member
User Online: User is Offline
Posted:14/03/2006 2:00 AM

Found this at a clients site.  If the web server is renamed with the gateway installed on the system you cannot run the server configuration wizard.

If you rename the server back to the earlier name, everything will work better.

However in certain instances if you rename the server before the software is ever installed it will install correctly, however the server config will never work.  This has been found in child domains with several domain polcies in place.  The only solution I have found in this case is to rebuild the server with the final name and then reinstall.

stucco

New Member
New Member
User Online: User is Offline
Posted:16/03/2006 3:19 PM

Had this same problem sprout up at another client's site.  They were migrating from their corporate domain to a new private sub domain, and when the server moved from one domain to another the server config tool no longer worked.

I was able to track down the problem to the com+ services that were registered to run as the domain admin account that is created during setup.  I tried manually moving the accounts to the new accounts in the new domain, to no effect.

The odd part was that the old domain was still accessible via a trust, so the accounts themselves should have been allowed to run.  To make things work again I took the following steps.

1> Remove the server component of AAC.

2> from dcomcnfg remove all references to the citrix AAC.

3> Reinstall the software with the new account pointing to the same database.  Match all the names for the setup as possible.

4> Install the patch if it was installed previously (necessary.)

5> Restore the Database from a SQL backup.

6> Redeploy the Logon point.

7> Change permissions for policies to new domain.

This got the portal back up and running with the same software and configuration as before.  Grand total of time for this process, about 15 minutes, so much faster then the current fix of rebuilding the machine from scratch.

You are not authorized to post a reply.


ActiveForums 3.0
  Home|Forums|Editorials|EPA Packages|Snippets
Copyright (c) 2009 SmartAccessCentral Terms Of Use Privacy Statement