summaryrefslogtreecommitdiff
path: root/cpp
diff options
context:
space:
mode:
authorMatthew Newhook <matthew@zeroc.com>2007-02-14 09:05:12 +0000
committerMatthew Newhook <matthew@zeroc.com>2007-02-14 09:05:12 +0000
commita6de42a08aa51474becbbb76894cbeeb32d4cdd3 (patch)
treec9c69acb2b7b864350f5bcf8013f75b348f5f847 /cpp
parentFix (diff)
downloadice-a6de42a08aa51474becbbb76894cbeeb32d4cdd3.tar.bz2
ice-a6de42a08aa51474becbbb76894cbeeb32d4cdd3.tar.xz
ice-a6de42a08aa51474becbbb76894cbeeb32d4cdd3.zip
added some vista specific instructions to WINDOWS_SERVICE.txt
Diffstat (limited to 'cpp')
-rwxr-xr-xcpp/install/windows/WINDOWS_SERVICE.txt70
1 files changed, 64 insertions, 6 deletions
diff --git a/cpp/install/windows/WINDOWS_SERVICE.txt b/cpp/install/windows/WINDOWS_SERVICE.txt
index 92ec4aac269..decace3cdc6 100755
--- a/cpp/install/windows/WINDOWS_SERVICE.txt
+++ b/cpp/install/windows/WINDOWS_SERVICE.txt
@@ -3,11 +3,11 @@ Installing IceGrid registry, IceGrid node or Glacier2 router as a
Windows Service
========================================================================
-Step 1: Review and edit the configuration file (icegridregistry.cfg,
+Step 1: Review and edit the configuration file (icegridregistry.cfg,
icegridnode.cfg or glacier2router.cfg)
-Step 2: Create the account for the user that will run the service
-(iceuser in the sample configuration files). This user should be
+Step 2: Create the account for the user that will run the service
+(iceuser in the sample configuration files). This user should be
initially Administrator (see note below).
Step 3: For the IceGrid registry or node, log on as 'iceuser' and
@@ -17,13 +17,22 @@ Step 4: Install the service, for example:
> icegridregistry --install IceGridRegistry \
--Ice.Config=C:\Ice-@ver@\config\icegridregistry.cfg
+On Windows Vista if UAC is enabled then the installation of the
+service requires administrator priviledges. To do this run the command
+shell as administrator. Right-click the cmd shell icon and select "run
+as admin".
+
Step 5: In the Windows Services panel, edit the new Service.
Change "Log on" to use the 'iceuser' account, instead of the Local
System Account.
-On Windows Server 2003, the user account that runs IceGrid node
-needs to be a member of the local 'Performance Monitor Users'
-group to be able to monitor the CPU usage of the system.
+Unless there is a password associated with the account under Windows
+Vista it will not be possible to start the service.
+
+On Windows Server 2003 and Windows Vista, the user account that runs
+IceGrid node needs to be a member of the local 'Performance Monitor Users'
+group to be able to monitor the CPU usage of the system. See below for
+a complete set of instructions.
Step 6: Start the service, and verify that the service starts
properly.
@@ -34,3 +43,52 @@ Step 7: Downgrade the 'iceuser' account to a regular Users account
Note: 'iceuser' needs to be Administrator the first time you start the
service if you log messages to the Windows Event Log (see the
Ice.UseEventLog property).
+
+Windows Server 2003 and Windows Vista
+-------------------------------------
+
+As previously mentioned the user account that runs the IceGrid node
+needs to be a member of the local 'Performance Monitor Users' group.
+
+These instructions have been taken from a Microsoft article contained
+at URL:
+
+http://technet2.microsoft.com/WindowsVista/en/library/ab3b2cfc-b177-43ec-8a4d-0bfac62d88961033.mspx?mfr=true
+
+First grant the user account "Log on as a batch job" rights.
+
+To assign the "Log on as a batch job" user right to the Performance
+Log Users group
+
+1. Click Start, click in the Search box, type secpol.msc, and press
+ ENTER. The Local Security Policy snap-in will open in Microsoft
+ Management Console.
+
+2. In the navigation pane, expand Local Policies and click User Rights
+ Assignment.
+
+3. In the console pane, right-click Log on as a batch job and click
+ Properties.
+
+4. In the Properties page, click Add User or Group.
+
+5. In the Select Users or Groups dialog box, click Object
+ Types. Select Groups in the Object Types dialog box and click OK.
+
+6. Type Performance Log Users in the Select Users or Groups dialog box
+ and then click OK.
+
+7. In the properties page, click OK.
+
+Next to update the group membership:
+
+Open the computer management tool. Select "Local Users and Groups",
+then "Groups", then "Performance Log Users". Then add the user to the
+members of this group.
+
+Or under an admin rights command shell:
+
+net localgroup"Performance Log Users""MemberName"/add
+
+Once this is done its necessary to logout and then login again if you
+are modifying the rights of the current logged in user.