In the mean time, you can do it by editing an XML file manually.

If you go to the Web Module’s data folder you will find a file called “Vantage Web Module.Reports”.  If you open this in Notepad, you’ll notice chunks of xml for each report:

<WebReport>
<Guid>89208266-42e5-44bc-baa2-157c404c9688</Guid>
<Title>Business Unit Report</Title>
<Date>633945813293343143</Date>
<Type>Analysis</Type>
<Access>
<Everybody>False</Everybody>
<Attributed>True</Attributed>
<Specific>True</Specific>
<SpecificEntities>
<item>person:CN=Luke,OU=Users,OU=Australia,OU=Webspy,DC=wsy,DC=com</item>
</SpecificEntities>
<Managers>True</Managers>
<ManagerLevelRestriction>3</ManagerLevelRestriction>
</Access>
<Attribution>person:CN=Scott,OU=Users,OU=Australia,OU=Webspy,DC=wsy,DC=com
</Attribution>
</WebReport>


Depending on how you published your reports, the unique ID of the person that currently has access to the reports will be mentioned in either the ‘SpecificEntities’ or ‘Attribution’ section.

You just need to find/replace this with the unique ID of the person you would like to transfer these reports to. You can find the unique ID of a person on the Organization screen in Vantage.  It’s called ‘Distinguished Name’:

Finding a user's unique ID in Vantage

A few more things:

• Make a backup of your original “Vantage Web Module.Reports” file before making any change.
• As you can see above, people need to be entered into this XML file using the syntax
  “person:<uniqueID>“
• You will also need to stop IIS before making any change as the web module caches this data in its memory while running.

As mentioned, creating a user interface to do this is a planned feature so follow us on Twitter, or subscribe to our RSS feed for updates!

To use Windows Authentication, there are just a few things you need to do.

1. Set the Web Module’s Authentication type to IIS Integrated, and add your administrators in the form of domain\username
2. Enable Windows Authentication and disable Anonymous authentication in IIS.
3. Ensure all users in your Organization screen have a login name in the form of domain\username. Use the ‘Prefix’ option to prefix “domain\” (without the quotes) to your usernames names when importing your Organization from LDAP or LDIF.
4. Connect Vantage and the Web Module using the new authentication details and synchronize your Organization.

1. Set the Web Module’s Authentication type to IIS Integrated, and add your Administrators.

When you first install the Web Module, the first screen you see is the ‘Initial Configuration Wizard’ that guides you through the process of selecting your authentication type and specifying your administrator(s). If you have already been through this Wizard and are currently using Vantage In-Built or Client Certificate authentication, you can easily reset this initial configuration wizard. Simply login to the Web Module with your current administrator details and go to Options | Maintenance | Reset Initial Configuration Wizard.

Note: You can also change your authentication and administrator options individually using the Authentication and Administrator options on the Options tab of the Web Module.  However, for ease of demonstration, I’ll use the Initial Configuration Wizard method.

Now that you’re at the Initial Configuration Wizard, proceed through the wizard, selecting IIS Integrated authentication and entering your administrators in the form of domain\username (replace domain with your organization’s AD domain, and username with the sAMAccountName of your administrator.

Initial Configuration Wizard - Welcome Page

Initial Configuration Wizard - Authentication Page

Initial Configuration Wizard - Delegate Administrators Page

Initial Configuration Wizard - Summary Page

Click Finish, and if the authentication was successfully changed, you should get a message saying ‘The specified credentials were not accepted”.

The 'Specified credentials were not accepted' message.

Don’t panic at this point. This message is an indication that the authentication was successfully changed and that the Web Module is now listening for IIS to pass through Windows Usernames. The reason you’re getting this message is because IIS is not yet passing through Windows Usernames to the Web Module. This is configured in the next step.

2. Enable Windows Authentication and disable Anonymous authentication in IIS.

Now that the Web Module is expecting IIS to authenticate your users, you need to set up  IIS  to do this.

1. Open IIS by navigating to Start | Control Panel | Administrative Tools and double-clicking on Internet Information Services (IIS) Manager.
2. Navigate to the Web Module site or virtual directory in the left hand ‘Connections’ Panel. It will be located under <Server Name>\<Sites>. For example, MyServer->Sites->Default Web Site->webmodule.

• If you’re running IIS7 ( Windows Server 2008, Vista or Windows 7)
  1. Select the Web Module site and ensure the ‘Features’ tab is selected at the bottom of the middle pane.
  2. Double-click the ‘Authentication’ feature.
  3. Right-click ‘Anonymous Authentication’ and select Disable
  4. Right-click and ‘Windows Authentication’ and select Enable
  5. Restart IIS by selecting your server in the right hand connections pane, and clicking Restart in the ‘Actions’ pane on the right.

• If you’re running IIS6 or 5.1 (Windows Server 2003, Windows XP)
  1. Right-click Web Module site and select Properties.
  2. Go to the Directory Security tab
  3. Under ‘Authentication and access control’ click the Edit button.
  4. Uncheck ‘Enable anonymous access’ and check ‘Integrated Windows authentication’
  5. Restart IIS by right-clicking the local server, select All Tasks, and then click Restart IIS.

If you added your own Windows login name as an administrator in step 1, you can now test the authentication is working. Go back to the Web Module in your browser and click Refresh. You will be presented with an ‘Authentication Required’ dialog where you can enter your username and password.

Authentication Required Dialog

Again, ensure your username is in the form of domain\username. Click OK, and you should log straight into the Web Module using Windows Authentication.

3. Ensure all users in your Organization screen have a login name in the form of domain\username

Now your administrator account can log into the Web Module using Windows Authentication, but all other users will not be able to log in unless they have their login name specified in the form of domain\username. This is done in Vantage Ultimate on the Organization screen.

Organization Screen showing correct login name for Windows Authentication

If you’re importing your users from LDAP or LDIF, make sure you use the ‘Prefix’ option on the User Details page to prefix domain\ before your imported usernames. For example:

4. Connect Vantage and the Web Module using the new authentication details, and synchronize your Organization.

In order to publish information to the Web Module, you need to add a connection between Vantage and the Web Module. This is done on the Web Module screen in Vantage Ultimate.

1. Click Add Web Module (or if you already had a web module before changing the authentication details, select it and click Properties)
2. Enter the server & virtual directory of the Web module, and enter the correct credentials ensuring domain is specified.
3. Click OK to connect.

Connect to Web Module dialog

Once connected, synchronize Vantage with the Web Module by clicking the Synchronize link in the Web Module task pad. You may also want to provide permissions for your users in the Permissions section on the Web Module screen.

That’s it. You can now test that everything is working by getting one of your users to access the Web Module’s URL. They should sail straight in with no username/password prompt.

I hope this helps! Please let me know your feedback by emailing me, or leaving a comment below.

• Windows Vista & Server 2008:
  C:\Users\<user profile>\AppData\Roaming\WebSpy\Vantage <edition> <version>
• Windows XP & Server 2003:
  C:\Documents and Settings\<user profile>\Application Data\WebSpy\Vantage <edition> <version>

When Vantage opens, it loads the information contained in these files.

To move all your settings across, you can simply copy all the files in this location on your original machine, into the same folder on the new machine (make sure Vantage is closed when you do this).

When you open Vantage on the new machine and you’ll have all your settings moved across.

If you’re using scheduled tasks, one thing to note is that copying these files will not recreate the Windows scheduled task jobs. To get your tasks functioning on the new machine:

• Go to the Tasks tab and double-click each scheduled task.
• Proceed through the wizard and make sure all the settings are correct.
• Enter your authentication details on the last page and click OK.

This will create a new Windows scheduled task job which should run as it did on the old machine.

Please note that this process only moves ’settings’ across to the new machine. If Storages and Reports were being written to a location on the old machine, then you will need to move these across to the Storages and Reports locations on the new machine (check Tools | Options | Paths for these locations).

Also take access privileges into account. If you’re old installation was set to create storages in \\server\mystorages, make sure the new machine also has write privileges to this location.

That’s pretty much all there is too it. Happy migrating!