Clarity

We are in the process of testing CA PPM 15.3. The resources who will be testing with MSP 2016 and Schedule Connect will continue to need MSP 2010 and 14.3 Schedule Connect until rollout of 15.3. Not all of the resources who will be testing are in the same location so test labs will not be available. Can we install MSP 2016 and Schedule Connect in a virtualized environment?

Hi Kevin,

If I have understood the question correctly then you can install MSP and Schedule-connect in Virtual Machines.

These virtual machines should be on a network so that the machines can connect to Clarity application.

Thanks 

Regards

Gaurav  

Yes, the question is not quite clear.
As CA PPM is used with a browser the user workstation/desktop can be on a virtual machine.

Likewise the server can also be on a virtual machine.

Regardless whether the server or the desktop is virtualized the MS Project and Schedule connect must be installed on the desktop. That is I agree with Gaurav - also on a user virtual machine .

Hello Kevin,

Could you please provide more details on this topic. It is not clear what is the requirement.  

As per my understand Yes, we can install MSP and Schedule-connect in Virtual Machines. Please make sure they all are on same network. 

Also when user perform the Uninstall of the CA PPM Microsoft Project (MSP) on there machine make sure they perform below steps. Sometime we have found user face some issue to uninstall the MSP. 

Sometimes, due to permission restrictions or other issues on the machine, some of the MSP components do not get uninstalled on their own. If that is the case, a manual uninstall is needed to remove the remaining components. Doing a clean uninstall / install is especially recommended if running into issues during an upgrade of the MSP Interface.

Follow below steps:

Below are the steps to do a clean uninstall:

1. Uninstall the following components from Control Panel:

CA PPM Microsoft Project Interface

CA PPM Schedule Connect

CAClarityAddin

2. Clean out the Registry

On the workstation, go to Start and type 'regedit' in the search field. Select regedit.exe

Select File -> Export and enter a File Name to store the back-up of the registry

Once finished creating a backup, delete the following keys if exist:

HKEY_CURRENT_USER\Software\Niku

HKEY_LOCAL_MACHINE\Software\Niku (You may need to drill down to the Wow6432 folder to get to the Niku folder: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Niku)

Please note that some of the keys may not exist; also, deleting each key will correctly delete all of their sub keys.

3. Go to Add/Remove Programs again and check that there is no trace left of the products that you have removed at step 1

4. Delete the following folders if they are listed (First make a backup of any views you may have saved in the folders if they are still there):

C:\CA\CA PPM MSPInterface

C:\CA\PPM Setups

C:\CA\PPM\CA PPM Schedule Connect

Please note that the folder location is dependent on where the MSP Interface was installed:

If you installed the 32 bit Interface, the folders may be instead found in: C:\Program Files (x86)

If you installed the 64 bit Interface, the folders may be instead found in: C:\Program Files

5. Clean out Visual Basic:

In MSP, go to View > Macros > Visual Basic Editor

Expand ProjectGlobal, Expand Modules

Delete the modules that start with either CA_ and Niku_ (Right click the module and select 'Remove ...' (Example below)

Click ‘No’ to the message that pops up ‘Do you want to export <Module Name> before removing it?’

–(That is asking if you want to export the files, which is not needed)

Expand Microsoft Project Objects, Double-click on Thisproject

Select everything in the right panel and delete it

Save and exit VB

6. Verify correct Trust Center Setting:

Go to File > Options> Trust Center > Trust Center Settings

Make sure "Enable all macros" is selected.

7. Reinstall the MSP Interface.

Ensure the bit level of the MSP Interface being installed matches that of MSP.

Also make sure the version being installed is the same version and patch level as that of PPM. It can be found in PPM by going to Home->Account Settings->Software Downloads.