Last post Dec 07, 2005 01:18 PM by FSmith_Aliant
Dec 07, 2005 10:06 AM|FSmith_Aliant|LINK
I am attempting to install the Provisioning Framework (Deployment tool, MPS engine etc). I have built two new servers (Windows 2003 Enterprise SP1, SQL Server 2000 SP4) named MPS01 and MPSSQL01. I am attempting to install the Deployment Tool on MPS01. THe
problem I have is that the Deployment tool was previously installed (then uninstalled) on another host in the same domain. When I run the deployment tool .msi, I get to the Deployment Tool Info dialog - the text boxes where I should enter the Config Server
Name, Config Share Name, MSI Server Name and MSI Share Name all have the values from the first install and cannot be changed. I have not been able to determine where these settings are stored (domain controller? policies?) How do I reset these, so that I
can correctly reinstall the Deployment Tool?
Dec 07, 2005 12:56 PM|jjstreic|LINK
I'm looking at the documentation and see the following. It looks like the configuration object is stored in the schema and can be modified by using the "File Locations" from the file menu. Is this working for you? I'm checking with our teams on how to
cleanly remove this info from the AD, but try the tool first, for sure.
Configure MSI, MPS Source, XML Configuration, and Log File Locations
The MPS Deployment Tool maintains two file paths to manage access to the MSI applications, MPS component source files, XML configuration data, and log files. These paths are maintained using the following Active Directory object so that subsequent
MPS Deployment Tool installations can discover these paths:
distinguishedName: CN=MPS Server Config Entity,CN=System,DC=objectCategory: CN=Application-Entity,CN=Schema,CN=Configuration,DC=objectClass: applicationEntityproperty: adminDescription
When you run the MPS Deployment Tool for the first time on your Provisioning Engine server, the tool detects that this Active Directory object is missing and then prompts you to provide the paths to the ConfigShare and MSIShare that you set
up during tool installation. This enables the tool to configure the Active Directory object with these locations for future tool sessions.
During subsequent sessions of the MPS Deployment Tool, you have the option of editing these share paths using the
File Locations command on the Files menu. When you launch this command, the
File Locations dialog box appears and enables you to set the path for the
Installer files and the Configuration/Log files by directly typing them in or by browsing to the locations.
Dec 07, 2005 01:18 PM|FSmith_Aliant|LINK
Thanks for the response. After I posted, I also initiated a support incident to sort this out and the following explanation and actions fixed the problem. My installation proceeded smoothly after I did this.
I am posting it here to share with others.
The Deployment tool uses an attribute in Active Directory to store these file locations and to ensure that only one copy of the tool is running at any one time.
Since the deployment tool was installed previously these settings are retained in active directory so that a subsequent install is able to pick up the values and ensure information about the deployment is not lost. Please see the product documentation section
"MPS Deployment Tool Installation” located in (Windows-based Hosting Infrastructure Technologies > Service Provisioning > Advanced Service Provisioning Topics > MPS Deployment Tool Functions) for more information about this behavior.
To resolve this issue, the simplest method is to remove this attribute “MPS Server Config Entity” and run the install again. To remove this entity you can use
“Active Directory Users and Computers” via the following steps.
This will remove the information pertaining to the pervious install and allow you to reconfigure the shares. Please note that the information contained in the
configuration share should be retained during uninstalls and re-installs as it stores information about the state of the deployment. If this is not a completely new install then please ensure that the contents of the configuration share are copied to the
new servers configuration share.