Ma visto che dobbiamo adeguarci… cerchiamo di farlo a COSTO ZERO!

Io ho risolto (sto risolvendo) così:

Installo rsyslog con logging su file sul logserver

Su un server linux CentOs 5.*

Questi sono i passaggi da seguire:


links "http://prdownloads.sourceforge.net/libdnet/libdnet-1.11.tar.gz?download"
tar -zxvf libdnet-1.11.tar.gz
cd libdnet-1.11
./configure
make && make install && ldconfig
wget http://download.icu-project.org/files/icu4c/4.0.1/icu4c-4_0_1-src.tgz
wget http://slackbuilds.org/slackbuilds/12.2/libraries/icu4c.tar.gz
tar -zxvf icu4c-4_0_1-src.tgz
tar -zxvf icu4c.tar.gz
cd icu4c
mv ../icu4c-4_0_1-src.tgz ./
./icu4c.SlackBuild
mv /tmp/icu4c-4.0.1-i486-1_SBo.tgz /root/
installpkg ./icu4c-4.0.1-i486-1_SBo.tgz
wget http://mesh.dl.sourceforge.net/sourceforge/open-vm-tools/open-vm-tools-2009.02.18-148847.tar.gz
tar -zxvf open-vm-tools-2009.02.18-148847.tar.gz
cd open-vm-tools-2009.02.18-148847
./configure --includedir=/usr/include/uriparser --without-x --without-icu
make


Dalla VIM cliccare su Inventory-> Virtual Machine -> Install VMware Tools
tornare sulla console


mount /mnt/cdrom
cp /mnt/cdrom/VMwareTools-3.5.0-123629.tar.gz /root/
tar -zxvf VMwareTools-3.5.0-123629.tar.gz
cd open-vm-tools-2009.02.18-148847/modules/linux/
for i in *; do sudo mv ${i} ${i}-only; tar -cf ${i}.tar ${i}-only; done
cp *.tar /root/vmware-tools-distrib/lib/modules/source/
cd /root/vmware-tools-distrib/
mkdir /etc/pam.d
touch /etc/rc.d/init.d/network
ifconfig eth0 down
ifconfig eth1 down
ifconfig eth2 down
rmmod pcnet32
./vmware-install.pl
vmware-config-tools.pl


Ringrazio marcpem per l’how to originale

Spero sia di aiuto a tutti.
Saluti


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
“ShowInfoTip”=dword:00000000


ed eseguirlo.

Riavviare il pc e le info non compariranno più.
Per rimettere tutto a posto come prima:


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
“ShowInfoTip”=dword:00000001


Spero vi sia utile.
Saluti

Il problema si risolve avviando il servizio portmap:

su redhat/centos:

/etc/init.d/portmap start


su slackware:

chmod ugo+x /etc/rc.d/rc.rpc
/etc/rc.d/rc.rpc start


http://openvpn.se/files/howto/openvpn-howto_run_openvpn_as_nonadmin.html

Mathias Sundman (mathias@openvpn.se)
2005-02-17
Rev 1.1

Introduction

With the current implementation of the TAP-Win32 driver included with OpenVPN, administrator privileges is required to open the TAP device. This means that openvpn.exe must be executed with administrator privileges. In many situations it’s un recommended to do your day-to-day work logged on with an administrator account. Especially corporate environments often have a policy that users should never have administrator rights even on their local machine. Fortunately there are a few ways to work around this so OpenVPN can be used even in these environments.

Here I present you with two ways to run OpenVPN / OpenVPN GUI as a non-admin user:

1) Use the OpenVPN Service

Included in the OpenVPN / OpenVPN GUI installation package there is a small service wrapper for OpenVPN. This service simply starts all configuration files it finds in the OpenVPN\config folder. If you want your OpenVPN tunnel to always be up, regardless of whether you are logged on or not, you can simply configure the OpenVPN Service to start automatically at boot-time. However it might be more convenient to be able to start and stop the tunnel when you want, which you can do by starting and stopping the service. For more information about the OpenVPN Service see the “Running OpenVPN as a Windows Service” section in INSTALL-win32.

The major disadvantage with this method is that there is no way to supply the OpenVPN Service with the password used to encrypt your private key. This means that you must use an un-encrypted private key when using this method. A way to get around the problem with having your private key lying unprotected on your hard drive is to import it to the MS Certificate Store and use the –cryptoapicert option to load it. Remember that the service is running as “Local System” (by default) so you must import the key/cert into the System account, not your user account. (There is work in progress to allow OpenVPN to access also user account key/cert’s). To load a key/cert into the System accounts CertStore you must use the Certificates MMC Snap-In, not Internet Explorer.

Give a normal user right to control the OpenVPN Service

Normally starting and stopping a service requires administrator privileges, but you can assign a normal user the right to control an individual service. You do this with the subinacl.exe utility included in the Windows Resource Kit. You can also download it here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=e8ba3e56-d8fe-4a91-93cf-ed6985e3927b&displaylang=en

To give the user “John” the right to start and stop the OpenVPN service, log on as administrator and run the following command:

subinacl /SERVICE “OpenVPNService” /GRANT=john=TO

You can also give a user right to control a service through the use of Group Policies. See this support article for more info.

Control the OpenVPN service from OpenVPN GUI

A default installation of OpenVPN GUI does not give you any way to control the OpenVPN service. There is however two ways to do this. If you are running as administrator, and just want a convenient way to control the OpenVPN Service, you can enable a hidden menu for this. You enable this by setting the following registry value to “1″:

HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI\allow_service

Since OpenVPN GUI 1.0-rc2 there is a special mode called “Service Only” that is suitable for users running without admin privileges. This mode changes the behavior of the “Connect” and “Disconnect” actions to start and stop the OpenVPN service instead of launching openvpn.exe directly, like it usually does. It also hides the “Proxy Settings” menu as it has no effect on the service. To enable this mode set the following registry value to “1″:

HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI\service_only

Also remember that a normal user don’t have write access to the OpenVPN\config folder, so he won’t be able to edit the OpenVPN config file or change his password, unless you give him write access to these files. To hide these menu items set the following registry values to “0″:

HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI\allow_edit

HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI\allow_password

2) Windows “RunAs” feature

Since Windows 2000, there is a feature that allows you to start an application as another user than the currently logged on account. The best way to use this feature is by starting OpenVPN GUI as administrator this way. Since OpenVPN GUI is then running as administrator any number of OpenVPN tunnels can started and stopped as long as OpenVPN GUI is running.

* Keep in mind that by using this feature you are potentially giving your users a way to escalate their privileges to administrator rights. If your main reason for not running as administrator is to protect against malicious code on the web from executing with administrator rights in your computer, then this could be a good way to run OpenVPN GUI, but if your users under no circumstances should be able to run other applications as administrator, you should NOT use this way to run OpenVPN GUI either!

While installing OpenVPN / OpenVPN GUI, make sure to un-check “AutoStart OpenVPN GUI”, as you will need to create your start-up shortcut manually.

Create a “RunAs” short-cut in Windows 2000

• Create a normal Short-Cut to openvpn-gui.exe (c:\program files\openvpn\bin\openvpn-gui.exe) on the desktop.
• Right-click the short-cut and select Properties.
• Check “Run as a different user”.

When you double-click this short-cut, you will now be prompted for the username and password of the user you want to run as. If you want OpenVPN-GUI to auto-start when you logon, move this short-cut to your “Startup” folder on the Start->Programs menu. You will then be prompted for username and password directly every time you log on.

I’m not aware of any way to save the credentials so you don’t have to type them every time in Windows 2000.

Create a “RunAs” short-cut in Windows XP

• Create a normal Short-Cut to openvpn-gui.exe (c:\program files\openvpn\bin\openvpn-gui.exe) on the desktop.
• Right-click the short-cut and select Properties.
• Click “Advanced…”
• Check “Run with different credentials”.

When you double-click this short-cut, you will now be prompted for the username and password of the user you want to run as. If you want OpenVPN-GUI to auto-start when you logon, move this short-cut to your “Startup” folder on the Start->Programs menu. You will then be prompted for username and password directly every time you log on.

Create a “RunAs” short-cut in Windows XP that saves the administrator password

WARNING: When using this method the user will be able to start ANY application as administrator with the right knowledge.

• Create a normal Short-Cut to openvpn-gui.exe (c:\program files\openvpn\bin\openvpn-gui.exe) on the desktop.
• Right-click the short-cut and select Properties.
• In the Target box, insert the following before the path to openvpn-gui.exe: “runas /savecred /user:administrator “.
• Double-click the new short-cut, and enter the administrator password.

Next time you run this short-cut, it will start OpenVPN GUI as administrator automatically without prompting you for any credentials. If you want OpenVPN-GUI to auto-start when you logon, move this short-cut to your “Startup” folder on the Start->Programs menu.

Future

There is work in progress to enhance the OpenVPN Service so it can be controlled via a TCP socket. This will allow individual tunnels to started and stopped at will, as well as supplying OpenVPN with the password used to encrypt the private key. OpenVPN GUI 2.0 will be rewritten to make use of this service.

Questo articolo vi arriva grazie alle gentili donazioni di “foucault66″ e “f.graniglia”.

L’Aduc ha pubblicato oggi un comunicato a proposito della controversia sul diritto negato al rimborso per Windows preinstallato e non utilizzato, come previsto da una poco nota clausola della licenza Microsoft. La questione (e il mio successo nell’ottenere il rimborso, seguito da quello di pochi altri testardi) è raccontata in dettaglio nella mia pagina apposita.

L’associazione di consumatori aveva denunciato Microsoft all’Autorità Garante della Concorrenza e del Mercato per abuso di posizione dominante, proprio perché è praticamente impossibile acquistare un PC senza Windows preinstallato (specialmente nel settore dei portatili e la clausola di rimborso prevista nella licenza viene sistematicamente boicottata da rivenditori e produttori. In questo senso, anzi, Aduc ha citato in giudizio HP e ha predisposto un modulo per la richiesta di rimborso.

Il comunicato Aduc di oggi cita la risposta dell’Autorità Garante, che non sono riuscito a trovare sul sito del Garante ma che secondo ADUC è in una “lettera 28300/06 del 27/7/2006″ nell’ambito del procedimento DC/5073 (sarebbe interessante leggerla per intero, ho già chiesto all’Aduc):

…L’Autorità, dopo la seduta dello scorso 20 luglio 2006, ci ha comunicato che secondo lei questo abuso non c’è: per Microsoft l’Autorità ritiene che quanto da noi segnalato non vi è riferibile, ma lo sarebbe per le imprese produttrici di hardware che pre-installano Windows nei computer. “Dalle informazioni raccolte –continua l’Autorita’ garante della Concorrenza e del Mercato- è inoltre emerso che sul mercato vi sono imprese che offrono prodotti che non installano tale sistema operativo e che comunque i consumatori possono rifiutare l’installazione di Windows e ricevere un rimborso”.

Microsoft non è colpevole, insomma, ma lo sono i rivenditori e i produttori che non consentono l’applicazione corretta della licenza. Al tempo stesso, le parole del Garante ribadiscono il diritto del consumatore a ricevere un rimborso.

Aduc riassume lucidamente il problema del rimborso. A parte la faccenda di arricchire ulteriormente Microsoft con un prodotto che il consumatore non vuole (perché vuole installare Linux o ha già una licenza valida di Windows) ma è costretto a pagare,

i consumatori vorrebbero poter scegliere “UN PC SENZA SISTEMA OPERATIVO” alla stregua di “UN VASO SENZA FIORI”; o perlomeno, i fiori vorrebbero poterli scegliere da soli!

Parole sante.

Tipo evento: Errore
Origine evento: ESENT
Categoria evento: Registrazione/Ripristino
ID evento: 412
Data: 7/6/2000
Ora: 14.56.53
Utente: N/D
Computer: ASKO-ONE
Descrizione: servizi (PID) Impossibile leggere l’intestazione del registro. Errore -530.

Event Type: Error
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 413
Date: 5/12/2005
Time: 2:46:16 PM
User: N/A
Computer: [computername]
Description:
wuaueng.dll (1280) Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.

ho stoppato il servizio “aggiornamenti automatici”
ho cancellato tutto il contenuto di
%windir%\SoftwareDistribution\DataStore\Logs\
TRANNE edb.chk

ho riavviato il servizio e dalla pagina di windows update ho scelto “modifica impostazioni”
e ho disattivato Microsoft Update.

Saluti

http://support.microsoft.com/kb/278316
http://support.microsoft.com/kb/296220

Gli ID evento ESENT 1000, 1202, 412 e 454 vengono registrati ripetutamente nel registro applicazione

Torna all’inizio

Si registrano i punti di indicizzazione che funzionano e i messaggi di evento ESE98

Torna all’inizio

Troubleshooting Client Setup

In some cases, AU clients do not show up in WSUS Administration console, and thus never receive updates from WSUS. There are several reasons why this can happen.

Reg query “HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate” /s

Ensure server and port number shown in the output exist and are correct. Typos in these settings can be the cause of your problem.

Next check whether WSUS is installed on Default Website. If client policies point to the default web site for updating, check that WUS is also installed in Default Website. If you have installed WUS on a different port run the script %Program Files%\MicrosoftWindowsUpdate\Services\”SetupInstallSelfupdateOnPort80.vbs.

Also, use the clientdiag tool from the RC (download this from the WSUS Beta Site) to see what other errors there might be.

If other computers are checking in fine but you have one or more that aren’t, check a couple relevant text logs for clues. There’s the main windows update log at %systemroot%\WindowsUpdate.log (WindowsUpdate all one word) and another log covering individual component updates at %systemroot%\SoftwareDistribution\ReportingEvents.log I found a handy page that has a list of error messages with some plain english messages. You’ll want to check that out at http://perso.wanadoo.fr/doc.jm/WU5-ERR.htm

I had one computer not checking in and found errors like this in the ReportingEvents.log:

and in WindowsUpdate.log I saw:

A quick visit to the beta v6 windowsupdate site updated the WU client and everything just started working from my local WSUS after that. You can force the client to restart the AU process by doing:

If client machines do not have web access, download the full file Windows Update Client agent Agent from
http://go.microsoft.com/fwlink/?LinkId=43264

WindowsUpdateAgent20-x86.exe /wuforce /quiet to install it remotely.

Add /norestart if you’re doing it during the day (my clients didn’t need a reboot, but ya never know).

If you’re seeing error 0×8024400A and are running WSUS on Win2K3 SP1 it might be an IIS bug that’s causing it.  A hotfix is available.  See: http://support.microsoft.com/Default.aspx?id=898708  

I personally had success via a “shotgun” aproach suggested by ctobio on the wsus.info forums.  I’ve consolidated the operations into a batch file form here, suitable for running remotely:

REM Stop the Automatic Updates service
net stop wuauserv

REM Roll the WU Client…
wuauclt /resetauthorization /detectnow

After you do this, you will have to delete the old and now spurious computer account in the WSUS admin interface.  Delete the old computer that shows a status of not having checked in for so many days.  Leave the account that’s never checked in.  This new account will be checking in and that should be reflected after a little while in the admin interface.  You’ll also have to move the new account into the proper group where the old one was.  Monitor the WindowsUpdate.log in %systemroot% on that client machine to ensure that it’s grabbing updates again.

If a client appears in the admin console but all the updates are flagged “unknown” the system cannot determine which updates are needed or installed. Multiple errors similar to the following may appear in the client’s Application event log:

Event Type: Error
Event Source: ESENT
Event Category: General
Event ID: 427
Date: 5/17/2005
Time: 10:51:44 AM
User: N/A
Computer: [computername]
Description:
wuaueng.dll (1280) The database engine could not access the file called C:\WINNT\SoftwareDistribution\DataStore\Logs\edb.log.

Additionally the following error may appear once around the time of the first occurrence of the above error:

Event Type: Error
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 413
Date: 5/12/2005
Time: 2:46:16 PM
User: N/A
Computer: [computername]
Description:
wuaueng.dll (1280) Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.

To resolve this problem, stop the Automatic Updates service on the affected client, delete %windir%\SoftwareDistribution\DataStore\Logs\edb.log and restart the service.

[I couldn't find any record of this error at Microsoft or anywhere else.]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUState  This will have one of the following values   

• 0—initial 24-hour timeout (Automatic Updates doesn’t run until 24 hours after it first detects an Internet connection.)
• 1—waiting for the user to run Automatic Updates
• 2—detection pending
• 3—download pending (Automatic Updates is waiting for the user to accept the predownloaded prompt.)
• 4—download in progress
• 5—install pending
• 6—install complete
• 7—disabled
• 8—reboot pending (Updates that require a reboot were installed, but the reboot was declined. Automatic Updates won’t do anything until this value is cleared and a reboot occurs.)

Comments:

From karmacop – 29/03/05 8.10

From ipelivan – 20/04/05 15.07

From jahovabob – 07/07/05 9.48

From helsby – 06/10/05 8.45

From rpaz – 08/01/06 17.42

From rpaz – 08/01/06 17.46

From rpaz – 08/01/06 18.00

From rpaz – 08/01/06 18.00

From rpaz – 08/01/06 18.13

From giadzich – 22/02/06 12.16

From weeble – 27/02/06 1.47

From laurin1 – 21/06/06 13.27

From geraghty – 11/05/07 6.39

You may need to turn off cache mode and turn it back on if your Outlook
client is running slow, or if you are suddenly unable to send or receive
emails. Going through the steps will essentially remove the Outlook
cache from your computer, and then rebuild it. The cache is the local
copies of your emails.

1. Turn Off Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Uncheck the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

2. Close Outlook
1. File
2. Exit

3. Delete OST files from hard drive
1. Start
2. Search
3. For Files or folders
4. All files and Folders
5. Expand "More Advanced Options"
6. Check the box next to "Search hidden files and folders"
7. Leave the other options at default
8. In the top box for "All or part of the file name", type in
"*.ost"
9. Look in should be "Local Hard Drives"
10. Click Search
11. It'll find files such as outlook.ost, outlook001.ost, etc.
Select all the files it finds and select delete. This will
delete all the offline emails from your computer, but they
are still on the server so you won't lose anything.

4. Turn On Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Check the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

5. Restart Outlook

Once Outlook is restarted, all of your emails will download to your
computer again. It may take awhile, depending on the number of emails
you have. You can watch the progress in the lower right corner of your
Outlook screen… it will show the folders as they update.

Try first to launch Outlook in safe mode (Outlook /safe).
If the problem disappear in safe mode, try first disabling add ins and
then try renaming cache files (source : newsgroups)

Locate and rename the Outlook cache files
(frmcache.dat,outcmd.dat,extend.dat) one by one.
————————————————–

1. Quit Outlook.
2. Click Start -> Search -> For Files and folders
3. Click Tools -> Folder Options.
4. Select View tab, select Show hidden files and folders, uncheck Hide
extensions for known file types, and click OK.
5. Click All files and folders.
6. Type "frmcache.dat,outcmd.dat,extend.dat,views.dat" (without the
quotation marks) in the filename box, and then select Local Hard Drives.
7. Click More advanced options, check Search hidden files and
folders, and
click Search.
8. After the search has finished, renames files in .old
NOTE: We may find multiple files for each name. Please rename them all.
9. Restart Outlook.

In caso invece vi fossero problemi hardware di altra natura, consiglio
la consultazione delle seguenti pagine Microsoft:

Hardware and Software Third-Party Vendor Contact List, A-K
<http://support.microsoft.com/?kbid=65416>
Hardware and Software Third-Party Vendor Contact List, L-P
<http://support.microsoft.com/?kbid=60781>
Hardware and Software Third-Party Vendor Contact List, Q-Z
<http://support.microsoft.com/?kbid=60782>

In qualche altra circostanza la causa del problema potrebbe dipendere
dal file di paginazione, e visto che non costa nulla, provare questa
procedura:

1. destro mouse su risorse del PC / proprietà /avanzate / impostazioni e
cliccare sul pulsante prestazioni / avanzate / memoria virtuale / cambia
/ qui selezionare nessun file di paging e cliccare su imposta / OK / OK
e riavviare

2. una volta riavviato destro mouse su risorse del PC / proprietà
/avanzate / impostazioni e cliccare sul pulsante prestazioni / avanzate
/ memoria virtuale / e selezionare Dimensioni gestite dal Sistema
cliccare Imposta / Ok / Ok e riavviare.

Se con questa procedura non compare più l'errore
DRIVER_IRQL_NOT_LESS_OR_EQUAL allora siamo stati fortunati, se invece
compare ancora e pure frequentemente, allora meglio focalizzare
l'attenzione sulla RAM.

fonte jsi

OpenOffice e JRE

thanks to
http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation

Desktop Software Installation

These instructions describe the steps needed to perform a network
installation of the OpenOffice.org office suite and the
OpenOffice-Enterprise client software using Windows Group Policy.

These instructions are copyright Open Office Technology. They may be
linked to but not copied. Their permanent location is

http://OpenOfficeTechnology.com/OpenOffice-Enterprise/Desktop_Installation

<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation>

* Overview <http://openofficetechnology.com/node/24>
* Package Installation Order <http://openofficetechnology.com/node/30>
* Step 1 – Download Software Packages
<http://openofficetechnology.com/node/25>
* Step 2 – Create Network Installation Images
<http://openofficetechnology.com/node/26>
* Step 3 – Create Installation Group Policy Object
<http://openofficetechnology.com/node/27>
* Step 4 – Set Policy Scope and Link to Domain
<http://openofficetechnology.com/node/28>
* Upgrading OpenOffice-Enterprise
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice-Enterprise>
* Upgrading OpenOffice
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice>
* Installation Troubleshooting <http://openofficetechnology.com/node/29>

Overview

The three software packages discussed in these instructions are:

1. The OpenOffice.org office suite. Installation of this package on
each client is required.
2. The OpenOffice-Enterprise client software. Provides Group Policy
management for the OpenOffice.org office suite. Installation of
this package on each managed client is required.
3. Sun's Java runtime environment (JRE). Certain functions in the
OpenOffice suite depend on the Java runtime, such as the database
application, mail merge and the document wizards in Writer. (For a
more complete list, see Java and OpenOffice.org
<http://wiki.services.openoffice.org/wiki/Java_and_OpenOffice.org#OpenOffice.org_2.0_Functionality_depending_on_Java>).
If these features are not required, the JRE does not need to be
installed. Full functionality requires the JRE or JDK version
1.4.0_02 or newer, or version 1.4.1_01 or newer. Limited
functionality is available with version 1.3.1 or higher. (Source:

http://www.openoffice.org/dev_docs/source/sys_reqs_20.html)

These instructions describe the installation procedure using the most
recent application versions as of the date these instructions were
written. The OpenOffice suite and Java JRE are not distributed by Open
Office Technology, and the information related to these packages may
change from time to time. If you find any discrepancies in these
instructions, please let us know <http://openofficetechnology.com/contact>.

Package Installation Order

The three packages must be installed in the following order:

1. Optionally, if required, the Java JRE.
2. The OpenOffice.org office suite.
3. The OpenOffice-Enterprise client software.

The installation of one or more of these packages can be combined into a
single Group Policy operation.

These instructions describe the process of installing all three packages
in one operation. If one or more are already installed, simply skip the
corresponding steps. To install one or more of the packages separately,
create separate Group Policy objects these packages.

Step 1 – Download Software Packages

The first step in the installation process is to download the software
packages.

A. Optionally, download the Java JRE *offline* installation package for
Windows. As of the date of these instructions:

* Most recent version of the JRE: Version 6.0
* Installation package file name: jre-6-windows-i586.exe
* Download location: http://java.sun.com/javase/downloads/

(Click to download "Java Runtime Environment (JRE) 6", click to
accept license agreement, then click on "Windows Offline
Installation, Multi-language")
* Other versions: http://java.sun.com/javase/downloads/previous.jsp

B. If OpenOffice is not already installed on the client machines,
download the OpenOffice installer for Windows without the JRE bundled.
As of the date of these instructions:

* Most recent version of the OpenOffice suite: Version 2.1
* Installation package file name: OOo_2.1.0_Win32Intel_install_en-US.exe
* Download location: http://download.openoffice.org/

* Other versions at: http://distribution.openoffice.org/mirrors/

<http://distribution.openoffice.org/mirrors/index.html#mirrors>

C. Download the OpenOffice-Enterprise client software installer. As of
the date of these instructions:

* Most recent version of OpenOffice-Enterprise client software:
Build 450
* Corresponding package file name: ooewin-450.msi
* Download location: http://OpenOfficeTechnology.com/download

<http://openofficetechnology.com/download>

Step 2 – Create Network Installation Images

The next step is to create network installation images for each of the
software packages. This places the installation images on a network file
server that is accessible to the client computers. To complete this
process, you must have write access to this location. The client
computer should have read-only access.

A. Extract the Java JRE msi file:

1. Run the JRE installation executable file, jre-6-windows-i586.exe.
The License Agreement screen will appear. Do not click either
"Decline" or "Accept".
2. The installer executable will have placed a file called
"jre1.6.0.msi" into the directory "C:\Documents and Settings\<your
username>\Application Data\Sun\Java\jre1.6.0". Copy the .msi file
to a network installation point, which is a location on the
network accessible to the client computers, such as
|
\\fileserver\net_install_images\jre-1_6_0\
|
Note 1: Earlier versions of JRE installation executable placed the
.msi file into a subdirectory such as "C:\Documents and
Settings\<your username>\Local Settings\Application
Data\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}", where the name of
the subdirectory depends on the JRE version. The .msi file
corresponding to the JRE version can be located by looking in all
subdirectories with names matching this pattern.
Note 2: Neither the Java installer executable nor the .msi file
support the "/a" administrative installation option.
3. Returning to the License Agreement screen, click "Decline". The
installer will delete the Application Data\Sun\Java directory and
its .msi file, then terminate.

B. Perform an administrative installation of the OpenOffice suite:

1. Run the OpenOffice installer,
OOo_2.1.0_Win32Intel_install_en-US.exe, with no parameters.
2. When prompted, enter a location to unpack the installation files,
such as a subdirectory called Ooo_installer_files in your current
working directory.
3. When the next stage of the installer runs ("Welcome to the
Installation Wizard for OpenOffice.org 2.1"), click "Cancel" and
abort the installation.
4. The OpenOffice installer should have unpacked several executable
and data files into the directory you selected. From the command
prompt, launch the setup file using the following command line:
|
setup /a
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\OpenOffice-2.1\
|
and then click "Install". The installer will create the directory
you specified, if it doesn't already exist, and then unpack the
file "openofficeorg21.msi" along with a handful of subdirectories
into this location.

C. Perform an administrative installation of the OpenOffice-Enterprise
client software:

1. From the command prompt, launch the installer file using the
following command line:
|
msiexec /a ooewin-450.msi
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\ooewin-450\
|
and then click "Next" twice. The installer will copy the .msi file
to this folder and unpack several files and one subdirectory.

Before continuing, ensure that the client computers have read-only
access to the network installation points that you used above.

Step 3 – Create Installation Group Policy Object

This step creates a Group Policy Object or "GPO" that will install the
software packages.

1. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then right-click on
"Group Policy Objects" and select "New". Enter a name such as
"OpenOffice-Enterprise Installation". Your new Group Policy Object
will appear in the tree under "Group Policy Objects". Right-click
on its name and select "Edit…". This will open the Group Policy
Object Editor.
2. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
3. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
4. Navigate to the network location where you placed the Java JRE
install file "jre1.6.0.msi" and double-click on this file. If you
are not installing Java, skip this step and move down to the first
package you are installing.
5. For the deployment method, select "Assigned". The JRE install file
should appear in the view pane.
6. Right-click on "Software Installation" and select "New –>
Package…" again.
7. Navigate to the network location containing your OpenOffice suite
administrative install, and double-click on the .msi file
"openofficeorg21.msi".
8. Several installation transform files are available here
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>.
If you do not want to use any transforms, select "Assigned" as the
deployment method and click "OK". The install file for OpenOffice
should appear in the view pane. Otherwise, to install OpenOffice
with one or more transforms, download the transform (.mst) files
and add them to the directory that contains the OpenOffice
installation file openofficeorg21.msi. Then for "Deployment
Method" select "Advanced" and click "OK". After a short pause, the
Properties dialog should appear. Under the "Modifications" tab,
add the transform file you wish to apply, then click "OK".
9. Right-click on "Software Installation" and select "New –>
Package…" again.
10. Navigate to the network location containing your
OpenOffice-Enterprise administrative install, and double-click on
the .msi file "ooewin-450.msi". For the deployment method, select
"Assigned". The OpenOffice-Enterprise install file should appear
in the view pane.

IMPORTANT: You must add the .msi files in the indicated order:
Java JRE, then OpenOffice.org suite, then OpenOffice-Enterprise.
The packages will appear in the view pane in alphabetical order,
but they will be installed in the order they were selected. The
indicated installation order is mandatory in order for all three
packages to be installed successfully.

11. To set additional options, double-click on each package name in
the view pane. For example, selecting "Uninstall this application
when it falls out of the scope of management" will cause the
applications to be automatically uninstalled if this group policy
object is deleted or unlinked. (Alternately, the software can be
uninstalled later by right-clicking on each package name and
selecting "All Tasks" -> "Remove…"). Any options selected must
be set for each package individually, so be certain to
double-click on each package name in succession and set the
desired options.
12. When done, double check your selections and close the Group Policy
Object Editor.

Step 4 – Set Policy Scope and Link to Domain

This final step selects the computers on which the software will be
installed. This involves designating a group or list of computers, along
with one or more domains or organizational units. The software will be
installed on a computer if it is both in the group that you designated
/and/ in one of the domains or organizational units you select.

The default is to "assign" the installation to all users which will
ultimately cause the software to be installed on all computers in the
selected domains, including servers and domain controllers. This is
probably not what you want.

A typical configuration will only install this software on desktop
workstations, not on domain controllers. Here are instructions to
accomplish this:

1. Back in the Group Policy Management console, click on the name of
your Group Policy Object (e.g., "OpenOffice-Enterprise
Installation" or whatever name you previously chose). In the pane
on the right, under "Security Filtering" in the "Scope" tab,
select "Authenticated Users" and click on "Remove".
2. Click "Add…", and in the dialog box that appears, under "Enter
the object name to select", type "domain computers" and click OK.
"Domain Computers" refers to all workstations in your domain; it
does not include domain controllers. It may however include
servers, so you should check the members of this group. In the
Group Policy Management view pane, click on the word "Domain
Computers", then click "Properties". In the Properties dialog,
select the "Members" tab. This brings up a list of the computers
in the "Domain Computers" group. If this group includes more
computers than desired, you can "Remove" this group and then
"Add…" computers individually, or you can create a custom group
using Active Directory Users and Computers. You can also select
computers using WMI filters, but this is beyond the scope of this
document.
3. When you are finished selecting computers, click on the name of
your Group Policy Object in the tree view again, and without
releasing the mouse button, drag the pointer to the name of the
domain or organization unit in which to install the software. The
pointer will change shape to a pointer with a "+". Release the
mouse button and click OK to link your Group Policy Object to this
domain. Repeat this process for any additional domains or
organizational units.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the software will be installed the next time the computer is
rebooted. The installation process will take several minutes.

Upgrading OpenOffice-Enterprise

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice-Enterprise client
software.

1. Download the new release of the OpenOffice-Enterprise client
software, as described in Step C of Download Software Packages
<http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step C of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit…". This will open the Group Policy Object Editor.
4. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
5. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
6. Navigate to the network location containing the administrative
installation of the new version of the OpenOffice-Enterprise
client software and and double-click on the .msi file
"ooewin-450.msi".
7. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
8. Under the "Upgrade" tab, click "Add…" and under "Package to
upgrade", select "OpenOffice-Enterprise" and click "OK". The
properties dialog will display the text "Replace
OpenOffice-Enterprise".
9. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove…"
10. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of the OpenOffice-Enterprise client software
will be installed the next time the computer is rebooted. The
installation process will take only a few seconds.

Upgrading OpenOffice

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice.org office suite.

IMPORTANT: If you are upgrading to the latest v2.1 release of
OpenOffice, you must first upgrade to the latest release of the
OpenOffice-Enterprise client software, ooewin-450.msi. Prior releases of
the OpenOffice-Enterprise client software are not compatible with
OpenOffice v2.1.

1. Download the new release of OpenOffice, as described in Step B of
Download Software Packages <http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step B of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Download the file Check_OOE.mst
<http://openofficetechnology.com/system/files?file=Check_OOE.mst>
and add it to the network installation directory.
4. Download any additional installation transform (.mst) files
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>
you would like to use, and add them to the network installation
directory.
5. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit…". This will open the Group Policy Object Editor.
6. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
7. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
8. Navigate to the network location containing the administrative
installation of the new version of OpenOffice and and double-click
on the .msi file "openofficeorg21.msi".
9. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
10. Under the "Upgrade" tab, click "Add…" and under "Package to
upgrade", select "OpenOffice.org 2.0" and click "OK". The
properties dialog will display the text "Replace OpenOffice.org 2.0".
11. Under the "Modifications" tab, add Check_OOE.mst and the other
transforms you downloaded earlier (if any), then click "OK". The
selected transforms will appear in the properties dialog.
12. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove…"
13. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of OpenOffice will be installed the next time
the computer is rebooted. The installation process will take several
minutes.

Installation Troubleshooting

There a several methods to obtain information about the installation
process:

1. Installation failure and success messages are logged in each
computer's Application Event Log.
2. Group Policy and software installation operations can also be
logged. For more information, see the manual section /Logging
Group Policy and/or Software Installation/.