| Once you have package the Agent and deployed it to client you might still be required to reconfigure settings and or add application definitions and or just everyday maintenance. The following details how to prepare the MetaFrame Password Manager Console administrate a MetaFrame Password Manger farm of Agents.
The first thing you will need to do if you want to reconfigure and or add settings to a group of MetaFrame Password Manager Agents is connect to the directory and import the current directory setting to the console. 1. Right click on the Directory node and click Connect To. 2. Verify the directory information is correct and click OK to continue. 
3. Right click on the FTU node in the right hand pane and click Bring to Console. 
4. Right click ENTLIST and click Bring To Console. 
5. To import the Agent Settings right click the Agent Settings node in the left pane, click Import and click From File. 
6. Select the Agent Settings .reg file that was saved earlier and click the Open button. 
7. You are now ready to administrate the MetaFrame Password Manager Agent through the directory and Administrative Console. 
If, for any reason, you uninstall and reinstall the MetaFrame Password Manager Agent then you will be required to manually delete a few items. You will be required to deleted the Citrix folder in the Application Data directory, C:\Documents and Settings\<username>\Application Data\Citrix\ You will be required to delete the HKEY-USERS\...\...\Citrix\MetaFrame Password Manager key including all its children. Reboot the server and or workstation. 
By now you would have created a vision, defined the scope, filled out the scope in to a full fledge project plan, designed and documented the MetaFrame environment, built and tested it and have finished the pilot only to come to the end of another phase and arrive at another checkpoint. The Implementation Phase Checkpoint document should contain the following sections: Preface Vision / Scope (Statement of Work) Infrastructure Assessment findings Proof of Concept assumptions and findings Server Design q Hardware Requirements q Operating Systems Requirements MetaFrame Access Suite Design q MetaFrame XP Architecture o MetaFrame XP Farm Design o MetaFrame XP Zone Design o MetaFrame XP Data Collector Design o MetaFrame XP Data Store Design o MetaFrame XP Load Management Design o Applications o MetaFrame Conferencing Manager Design o MetaFrame XP Printing Design q Application Delivery Architecture o MetaFrame XP Web Interface Design o MetaFrame Secure Access Manager Design o MetaFrame XP ICA Client Design q Security Architecture o Secure Gateway for MetaFrame Design o MetaFrame Password Manager Design Infrastructure Design q File Storage q Logon Scripts q Infrastructure Modifications Implementation Phase Installation Steps (to reproduce the MetaFrame Access Suite deployment) Now that you have completed the Implementation phase, you will be ready to call another meeting, present your findings, and request to move on to the Readiness phase. At this point, your customer can choose to continue with the project or bow out gracefully. If the customer chooses to bow out then you would have earned a few service dollars and a significant amount of additional knowledge and experience. You will have also left the customer and yourself with the knowledge that you are now a consultant and not just a break/fix engineer. If the customer chooses to continue forward with the project then you will move forward to the Readiness phase. |