After attempting to install the most recent version of Polycom PVX software on a brand new Windows Vista machine, I found that there were horizontal lines all over the picture and some major lag. I looked through all the support documents and tested with two other cameras.

Finally I gave up and called Polycom Support [1-888-4143]. They explained that there was a new version that wasn't yet public. Great! So here is the currently super secret link.

www.polycom.com/support/pvx804

From the release notes:

PVX 8.0.4 delivers the following upgrades and modifications for PVX users:

• Support for Microsoft Vista Business and Enterprise editions
• Enhanced support for dual core Intel and AMD processors
• Fixes for priority field issues (see release notes for details)
• Upgrade support is provided in English only

External Links:

www.polycom.com/support/pvx804 - the site that I'm talking about http://downloads.polycom.com/video/pvx/804/PVX_8_0_4_4035.zip - the direct link to the newest software

This is a really simple way of moving public folders from one Exchange server to another that doesn't involving using Microsoft's PFMigrate Tool. That doesn't mean that this is the best way but when you have a small site or even a big complicated site that you don't want to go through the hassle configuring each site to talk to one another, this comes in handy. The way that I outline below does not take into account any permission structure so it will need to be recreated after the migration. Here is an over view:

• Copy the source public folders to an individual mailbox folder
• Export the folder to a PST
• Import the PST into a target mailbox
• Copy the folder to the existing public folders of the target environment

Setup:

1. Find the file size of the information store so that you know how much information you'll be transferring.
   1. You can do this by opening outlook that is connected to the Exchange server,
   2. right click on the public folder you want to migrate, choose properties.
   3. Then click the "Folder Size" button in the lower right corner. Make note of the "Total Size:"
2. Choose a migration mailbox that you will use on the source and target [this can be your personal one if you want]
   
3. Log onto the source exchange server and make sure that the mailbox supports the size of the public folders
   
4. Do the same on the target Exchange server
   
5. while you're logged in, also make sure that you've been granted rights to add files to the public folder

Export From The Source:

1. Connect to the source Exchange server from Outlook
   
2. create a folder in your personal mailbox that will store a copy of the public folders
   
3. Open the public folders you want to migrate
   
4. right click the folder you want to copy and choose "Copy FolderName"
   
5. Choose the folder in the personal mailbox that you created previously
   
6. After the copy is complete, go to File>Import and Export
   
7. Choose Export to a file and then Personal Folder File
   
8. Select the personal folder that now contains all of the public folders and click Next
   
9. Choose a location to export it to and click finish
   

Import To The Target:

1. Create a new profile in Outlook and connect to the target Exchange server
   
2. go to File>Import and Export
   
3. Choose "Import from another program or file"
   
4. Select Personal Folder File and click next
   
5. Choose the PST that you just created and import the files into your local mailbox under a sub folder somewhere
   
6. Drag the folder that you just imported into the public folders of the target exchange server

External Links:

http://support.microsoft.com/kb/822895 - PFMigrate - the Microsoft supported way of migrating public folders. This is great tool that pays more attention to detail than the way that I did it

I put together this process during a string of Exchange migration projects and it's really come in handy. There are hundreds of scenarios why you would want to automatically create the outlook profiles on logon.

One would be you are the system administrator of 100's of users and you're adding a new Exchange server. Rather than going around to explain to everyone the exchange server to type in to connect to, or having someone go around to 1000 workstations, you can script it like below.

Another would be as a sys admin, you have users that are switching workstations often and you're tired of all the calls complaining "My email doesn't work on so-and-so's machine" because they don't know how to set up their Outlook profiles.

Here's an overview of the process:

• Create a PRF that has all of the settings you want for the end users
• Create a logon script and apply it through a group policy to the end users
• The script runs at user logon and reads a registry entry to see if it has ever ran before [if it has then it quits]
• If this is the first time, it imports the PRF with all of the settings for the company automatically

Creating the PRF:

A PRF is a file that stores all the information for Outlook to create a profile for a user. There is no way to set the exchange server or which mailboxes to open through group policy so you have to rely on PRF files for administration and installation.

In this example, all I'm doing is pointing out where the exchange server is and that cached mode should be enabled. When you look at the Office Resource Kit [ORK] you will see that there are a lot more settings that you can play with than just the few here.

Here's what you need to do:

1. Download Microsoft Office Resource Kit [ORK] and install it on any workstation
2. Open the “Custom Installation Wizard” from the Start menu
3. When prompted, point to an Office 2003 Installation source. Either an administration point on the network or a CD will do.
   
4. Then when prompted choose, "Create a new MST" and click "Next.".
5. At the top right of the window, click the drop down and skip to step 17 “Outlook: Customize Default Profile”
   
6. Create a new profile and name it appropriately. Remember what you named it, you will need it to edit the script later
   
7. Configure the settings appropriately with the Exchange server, whether or not you want “Cached Mode” and whatever other site specific settings you need
   
8. Click Next and Next again to go to the “Export Profiles Settings” screen
9. Click the “Export Profile Settings” button and save the PRF to a place on the network [\\server\share\ORK_profile.prf]
10. Make sure that you test it on a workstation by running this command:
    OUTLOOK /importprf \\server\share\ORK_profile.prf

EDIT: Thanks to Oliver for catching a colon that shouldn't be there.

Creating a Logon Script To Install The Outlook Profile

So there is a PRF file created that has all of the necessary settings and it has been tested to make sure that it works. Instead of running that command individually for each of the hundreds of users on the network, it's scripted.

This script [compared to a batch file] not only runs the command, it checks to see if the command has ever been run before and if the profile has already been created. If it has, then it exits and that's it. If it has not, it imports the PRF file and then adds a registry setting so that it never runs again.

Disclaimer: There are a ton of ways you can do this but the end result should be that the script below runs on each machine. You could just instruct the users to run the script manually but this way, when a new user is added to the network, they will automatically have their profile set up.

Here's an overview of one way to set it up:

1. Copy this script to a text file and then save it as a .VBS to make it a vbs script: '*************************************************** ' File: auto_outlook.vbs ' Author: Mark M Manning ' Date: 10/10/2007 ' Version: 1 ' Based on the work of Peder Pedersen - pep@deif.com '*************************************************** Option Explicit Dim Company, PRFLocation, ProfileName ' ========================================= ' ====== EDIT THIS INFORMATION============= Company = "CompanyName" ' SET THE NAME OF YOUR COMPANY PRFLocation = "c:\test.prf" ' SET THE LOCATION ON THE NETWORK OR LOCAL DRIVE 'PRFLocation = "\\SERVER\share\test.prf" ' OF THE PRF THAT HAS BEEN CREATE ProfileName = "Site_Profile" ' This is the name that you have already ' created when you made the PRF. ' make sure they are the same ' ========================================= ' =================DO NOT EDIT ANYTHING BELOW THIS SECTION================ ' ======================================================================== Set WshShell = CreateObject("WScript.Shell") Set WshNetwork = Wscript.CreateObject("Wscript.Network") Set fso = CreateObject("Scripting.FileSystemObject") Set ObjEnv = WshShell.Environment("Process") Set objShell = CreateObject("Shell.Application") Set objSysInfo = CreateObject("ADSystemInfo") Set objUser = GetObject("LDAP://" & objSysInfo.UserName) Const HKEY_CURRENT_USER = &H80000001 Dim HKCUfirstRunflag HKCUfirstRunflag = "HKCU\Software\" & Company & "\FirstRunFlag" Dim HKCUprofile HKCUprofile = "HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\" & ProfileName Dim WshShell, WshNetwork, objEnv, fso, objShell, username, key, FirstRunCurrentUser, MSOKey, NoProfile, OfficeInstalled, strUserName, strInitials Dim strOfficePath, strMachineName, objSysInfo, objUser Dim objWord, LogonSrv, PRFPath, result, OSnummer, objWMIService, colOperatingSystems, objOperatingSystem strOfficePath = "Software\Microsoft\Office\11.0\Common\UserInfo" 'Path for office user info strMachineName = "." ' ============== START OF MAIN SCRIPT ============== 'Check OS ' ========================================= Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strMachineName & "\root\cimv2") Set colOperatingSystems = objWMIService.ExecQuery _ ("Select * from Win32_OperatingSystem") For Each objOperatingSystem in colOperatingSystems result = objOperatingSystem.Version OSnummer = Left(result,3) if OSnummer <> "5.1" then 'Wscript.Echo "This is not XP" 'Debug Wscript.Quit else 'Wscript.Echo OSnummer 'Debug end if Next ' ========================================= 'Test to see if the script has run before ' ========================================= TestfirstRunUser ' Has script been run before? If FirstRunCurrentUser then 'If not then continue TestProfile If NoProfile then 'Set up profile if none exists OutlookSetup 'Setup Outlook profile End if end if ' ========================================= ' Add a registry key if the script runs successfully WshShell.RegWrite HKCUfirstrunflag, "1", "REG_DWORD" cleanup ' ================================================ ' ============== END OF MAIN SCRIPT ============== ' ================================================ ' -------- Test if first run for this user? Sub TestFirstRunUser on error resume next 'cannot be read first time key = WshShell.RegRead(HKCUfirstRunflag) If Err <> 0 Then FirstRunCurrentUser = True Else FirstRunCurrentUser = False End If On Error Goto 0 End Sub '------------ Test if profile exists? Sub TestProfile on error resume next 'cannot be read first time MSOKey = WshShell.RegRead(HKCUprofile) ' determine if a profile has already been setup If MSOKey = "" Then 'wscript.echo "No Profile" 'Testing NoProfile = True else 'wscript.echo "Profile exists" 'Testing NoProfile = False end if On Error Goto 0 End sub Sub OutlookSetup WshShell.Run "outlook.exe /importprf " & PRFLocation, 1, False End Sub Sub Cleanup Set WshNetwork = Nothing Set objSysInfo = Nothing Set WshShell = Nothing Set fso = Nothing Set ObjEnv = Nothing Set objShell = Nothing Set objUser = Nothing Set objWord = Nothing Set objWMIService = Nothing Set colOperatingSystems = Nothing Set objWord = Nothing End Sub
2. Edit the script under where it says "EDIT THIS INFORMATION" [see Step #6 above]
   For instance:
   Company = "CompanyName" ' SET THE NAME OF YOUR COMPANY PRFLocation = "\\server\share\ORK_profile.prf" ' SET THE LOCATION ON THE NETWORK OR LOCAL DRIVE ProfileName = "YOURSITEPROFILENAME"
   
3. Save the vbscript to the netlogon folder or somewhere appropriate on the network [\\domain.local\netlogon\auto_outlook.vbs]
4. If necessary, create a group policy to apply the new logon script [or edit an existing one to add this script.]
   
   4a. [OPTIONAL] If you have some kind of software on the clients that protects against using vbscript at logon, already have an existing batch script that runs at logon, or like some admins I know are just against using vbscripts at logon completely, you can call the script from a batch file by running the "CScript" command. Include the command as something like this:
   
   cscript \\domain.local\netlogon\auto_outlook.vbs
   
5. Test by running your logon script from a workstation. Check the following
1. The registry key was created [HKCU\Software\%COMPANY%\FirstRunFlag
2. The profile with the appropriate name was created [even if a profile already exists]
   Control Panel > Mail > Show Profiles
   
3. The exchange server and information is configured correctly

External Links:

http://office.microsoft.com/en-us/ork2003/HA011402581033.aspx - Link about using PRF files

http://www.microsoft.com/downloads/details.aspx?FamilyID=4bb7cb10-a6e5-4334-8925-3bcf308cfbaf&displaylang=en – download the Microsoft Office 2003 Resource kit