OpenOffice 3.3 problem with msi administrative installation on windows 7

To install OO 3.3 VIA GPO with msi package we should modify msi package with orca

We need to modify Condition:

LaunchCondition (VersionNT =< 601) or (SETUP_USED=1) or Installed Informations about conditions we can find on this page http://blogs.flexerasoftware.com/installtalk/2010/11/using-msi-launch-conditions-to-prevent-installation-on-unsupported-windows-platforms.html

Security Warning when run application from network share

Problem:



Open File - Security Warning

The publisher could not be verified.

Are you sure you want to run this software?





Solution:

- Run gpedit.msc

- User Configuration > Administrative Templates > Windows Components > Attachment Manager > Inclusion list for moderate risk file types > Properties > Enable (and set the *.exe in edit box)

Konfiguracja Gnokii i nokia 2330

Nokia 2330 działa z kablem do nokia 2630 ( idVendor=067b)

W systemie wykrywana jest jako urządzenie


[ 3481.040082] usb 3-2: new full speed USB device using uhci_hcd and address 4
[ 3481.200986] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
[ 3481.200994] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3481.200999] usb 3-2: Product: USB-Serial Controller
[ 3481.201003] usb 3-2: Manufacturer: Prolific Technology Inc.
[ 3481.203173] pl2303 3-2:1.0: pl2303 converter detected
[ 3481.215151] usb 3-2: pl2303 converter now attached to ttyUSB0


tworzymy plik konfiguracyjny w katalogu domowym

touch .gnokiirc


i zapisujemy konfigrracje


connection = dku5
#use_locking = no
port = /dev/ttyUSB0
model = 6510


nastepnie sprawdzamy komunikacje z telefonem:


gnokii --identify
GNOKII wersja 0.6.26
IMEI : 355362043324552
Producent : Nokia
Model : RM-512
Nazwa produktu : RM-512
Wydanie : V 09.85

---

Przykładowe opcje:

- ściagamy wszystkie pliki jpg z domyślnego folderu zdjęć

for x in `gnokii --getfilelist "A:\\predefgallery\\predefphotos\\*" | grep .jpg`; do gnokii --getfile "A:\\predefgallery\\predefphotos\\$x" foto-$x; done;

---

- wyświetlamy info n/t godziny alarmu

gnokii --getalarm
GNOKII wersja 0.6.26
Alarm: wyłączony

---

- ustawiamy godzinę alarmu

gnokii --setalarm 05 00

---

change ssh V1 to V2 remontly (form ssh session)

First we should change RSA key to

fw1(config)#crypto key generate rsa

We get an warning that's current certificate will be removed and we confirm this warning.
In next step we set up

fw1(config)#ip ssh version 2

Finally we save all changes to nvram

fw1#copy running-config startup-config

TSM - ANR1163W messages

If we get ANR1163W message as shown below:

ANR2753I (MAINTENANCE):ANR1163W Offsite volume 018FFFL3 still contains files which could not be moved.

we can bring this volume onsite and mannually move data to other volume.
first we check for volumes in library

AUDIT LIBRARY BIBLOTEKA_LTO3 CHECKLABEL=BARCODE
CHECKIN libvol BIBLOTEKA_LTO3 search=yes checklabel=barcode status=PRIVATE WAITTIME=0

In next step we move data from this volume

tsm: TSM01>move data 018FFFL3
ANR2232W This command will move all of the data stored on volume 018FFFL3 to
other volumes within the same storage pool; the data will be inaccessible to
users until the operation completes.

Do you wish to proceed? (Yes (Y)/No (N)) y
ANS8003I Process number 256 started.

If this error is repeated every day or from time to time we should check if time for reclamation process isn't too short.
In this case we can limit number of tape to process like shown below

RECLAIM STGPOOL COPY_POOL WAIT=YES THRESHOLD=50 DURATION=600 OFFSITERECLAIMLimit=4

TSM konfiguracja DMR

Bieżącą konfigurację wyświetlamy komendą:

tsm: TSM01>q drmstatus

Recovery Plan Prefix: RECPLAN_
Plan Instructions Prefix: INSTRUKCJA
Replacement Volume Postfix: @
Primary Storage Pools:
Copy Storage Pools:
Active-Data Storage Pools:
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 5 Day(s)
Recovery Plan File Expiration Days: 5 Day(s)
Check Label?: Yes
Process FILE Device Type?: No
Command File Name:

Ważnymi parametrami konfiguracji DRMa są:

DB Backup Series Expiration Days - czas po którym usuwane są stare kopie bazy
The minimum number of days that must elapse since a database series has been created before it is eligible to be expired. See the SET DRMDBBACKUPEXPIREDAYS command for information about the criteria that must be met for database backup series expiration.
Czas ten określa się za pomocą

Set DRMDBBackupexpiredays days

Recovery Plan File Expiration Days - czas po którym usuwane są stare kopie planów recovery
The minimum number of days that must elapse since a recovery plan file, stored on a target server, has been created before it is eligible to be expired. See the SET DRMRPFEXPIREDAYS command for information about the criteria that must be met for recovery plan file expiration.
Ustawianie wartości za pomocą:

Set DRMRPFEXpiredays days

Process FILE Device Type?
Whether MOVE DRMEDIA or QUERY DRMEDIA commands process database backup and copy storage pool volumes associated with a device class with a FILE device type. Possible values are Yes or No.