Roaming Computing System (Windows Edition) 3.4
Workstation Installation Instructions
Supplemental Guide for Major Proprietary Applications
Introduction
This document is a supplemental guide to the workstation installation guide describing per-workstation installation and configuration of various major proprietary / commercial applications that are likely to only be required on particular workstations, and few workstations at that.
These applications are best installed manually from CD/DVD rather than through the WPKGpackage management system.
Adobe Creative Suite
Installation
Install on workstation
Install Photoshop, InDesign, Illustrator, Acrobat etcetera
Install updates
Register the program
Co-operative Bank Financial Director
Install on an accounts workstation from CD
Install whilst speaking with the bank
Install update
Dreamweaver
Installation
Install from CD
Install update
Register the program
The recommended preference for Dreamweaver site cache is to turn it off because, at least with version 8, it saves it in the user profile in a part that roams.
InDesign (upgrade edition)
Installation
Install on workstation
Install update
Register the program
Photoshop 7.0
Installation
- Install Photoshop 7.0 on workstation
- Choose Custom
- Select Photoshop Program Files
- Select Shared Plug-ins
- Select Photoshop Only Plug-ins
- Select ImageReady Only Plug-ins
- De-select Samples
- Select Preset Libraries
- Select Helpers
- Select Help
- Select Adobe Online (can't change it anyway)
- Select Adobe Type Support (can't change it anyway)
- Select ICC profiles (can't change it anyway)
- File type associations to change: Photoshop raw data (RAW) select for 'PS'
- Run it
- Set 'primary Scratch' to E:\%USERNAME%\photoshop?
- Install update - Run Photoshop 7.01 update
Quickbooks
Installation
Install on any accounts workstations from CD
QuickBooks 2008 requires .NET 1.1, QuickBooks 2006 may have brought in .Net Framework 2.0Update
Types of updates: Maintenance Releases; Regular.
QuickBooks 2006 and 2008 will update without first registering it. Some older versions need you to have opened a company file in order to be able to update (I think).
File → Update QuickBooks → Update → blank → Get Updates → explains something about trying to make connection → OK → Quit QuickBooks → it asks if you want to install the update.
Configuration
QuickBooks needs to run as a Power User. For details of why QuickBooks is so broken in this regard see 'QuickBooks Vista problems are six years in the making' and 'Error: "Windows XP and Windows 2000 users must have Power Users or Administrator group rights in order to run QuickBooks."'. See also Banks Urge Businesses To Lock Down Online Banking .
This configuration method involves running QuickBooks with elevated priviliges, creating a Power User account but only using it to run QuickBooks as a Power User, rather than logging in with the Power User account and using it for everything. QuickBooks needs access to either the shared directory (S:) or the restricted directory (R:), depending on where you want to save the company file (R: is recommended); and access to any printer shared from the server, so needs a domain account.
If the company file is to be saved on S:, in the Windows logon script on the server, to the S: drive mapping add /PERSISTENT:YES.
If the company file is to be saved on R:, in the Windows logon script on the server, to the R: drive mapping add /PERSISTENT:YES.
We do this because otherwise the user we run QuickBooks as has no S: or R:, though they can navigate to \\server\shared or \\server\restricted\finance. I expected runas's /env switch would fix this, but QuickBooks doesn't run when I use that. Instead I got S: or R: by adding '/PERSISTENT:YES' to the drive mapping in the logon script and logging in once with the power user account in order to save that drive mapping to their environment. Alternatively we could do without S: or R: and have the user access there by navigating to the company file through network neighborhood, QuickBooks thus saving to a UNC path
On the server
- Create a new domain user account.
- Give the new domain user account a strong password.
- If the company file is to be saved in R:\finance, and if you don't already have one, create a new restricted group called finance using Twix: R → F →.
- If the company file is to be saved on S:, or if access to S: from within QuickBooks is desirable anyway, make the power user account a member of <organisation>-staff using Twix: R → O.
- If the company file is to be saved on R:\finance, make the power user account a member of the finance restricted group using Twix: R → O.
On the Workstation
- Logon to the workstation on which QuickBooks is installed with an administrative account.
- Give the power user account Power User status by following see http://thegoldenear.org/toolbox/unices/samba-3-pdc-print-server-debian-etch.html#workstation-power-users.
- If there isn't already a desktop shortcut visible to everyone then create a new one in All Users (with permission for Users(?) to execute, probably the default when saved in All Users)
- Change the QuickBooks desktop (and possibly Start Menu) shortcuts, using either of these methods:
- a) (recommended)
- Alter the shortcut's Target to: runas /user:<domain>\<username> /savecred "C:\Program Files\Intuit\QuickBooks Pro\qbw32.exe".
The savecred switch is available in Windows XP Pro and onwards, not Windows 2000.
When this shortcut is first run it asks for the password for the power user account. This password is remembered for the particular user account you're logged in with.
If you don't want the password to be saved then don't use the /savecred switch, leaving users to enter the finance account password each time they run QuickBooks.
- b)
- Shortcut → Advanced... [*] Run with different credentials / right-click on the QuickBooks shortcut and choose 'Run as...'
- This prompts you each time you run the shortcut: "Which user account do you want to use to run this program?" () The following user: ...
Register QuickBooks
Register the program. Sometimes you may be asked to telephone Intuit for them to confirm the registration.
Power User Account Configuration
Login once with the power user account in order to have the S: or R: drive mappings saved to their environment.
QuickBooks needs Internet Explorer's Internet and Local Intranet zones to remain slack so don't configure the power user account using TWEAK.
User Who'll Use QuickBooks
Login as the user(s) who'll use QuickBooks on this workstation. Run QuickBooks and enter the password for the power user account and it will be remembered for this particular user.
If you're using R:\finance for files other than the QuickBooks company file (such as for exported spreadsheets and word processing documents) then also make this user a member of the finance restricted group (access to the company file on R: is already available through the power user account that QuickBooks is using).
RefsBase
- Login as winadmin
- If the operating system hasn't been setup using AutoPatcher, such as with our current Windows XP setup, then make sure .NET 2.0 is installed
- ? how do we get the refsbase shortcut now? or first run it from the server to get it installed locally?
- Run RefsBase using the desktop shortcut, it will install program files locally
- Enable write access for Users to the Refsbase program directory so settings files can be edited and new program versions installed: TWEAK: B → X
- If this system has had Outlook Express completely removed you need to re-install cdosys.dll
by copying it from S: [we should instead keep it in windows-admin] to %WINDIR%\SYSTEM32;
then register it using
regsvr32 "%WINDIR%\system32\cdosys.dll" /s.
Skype
Installation
Use 'Skype for Business' version.
- Choose the following components
- Skype - yes
- Skype Plugin for Interent Explorer - entire feature will be unavailable
- Skype extension for Firefox - yes
- when asked to sign up or sign in, choose cancel
- Welcome to Skype -> [] Start Skype when computer starts -> close window with X
- Say OK to finishing the installation
Microsoft Office 97
System-wide Configuration
Elevate the user's privileges temporarily:
net rpc group addmem "Domain Admins" <username> -U winadmin
Run the installer to configure it for both the user and for the workstation
- on the server P:\MSOffice\Setup.exe
- Enter the product key
- Choose 'Run from network server'
- The installer gives error messages about not all network resources being available
- Windows XP additionally has the error message: "HTMLMARQ.OCX was unable to register itself in the system registry" and then says the setup was not completed successfully. In this case you can only run Microsoft Office 97 direct from P:.
Slacken permissions for spell and grammer checker to work: TWEAK: B → Y
Remove temporary permissions elevation:
net rpc group delmem "Domain Admins" <username> -U winadmin