Agregátor zpráv

license:  Free (subject to disclaimer)

ZENworks Full Disk Encryption supports the use of a Windows PE emergency recovery disk to regain access to encrypted devices. Creating a Windows PE disk is an extensive command-line activity that requires the entry of more than 30 commands to create the correct directory structure and add the appropriate registry entries.

The Windows Powershell script automates the creation of the Windows PE emergency recovery disk, reducing the time required to create the disk and eliminating possible mistakes.

The result of the script is a Windows PE ISO image that you can burn to a CD or DVD.

Prerequisites:

1. Install the Windows Automated Installation Kit (AIK). The script expects the AIK to be located at C:\Program Files\Windows AIK. If you do not install it to this location, you will need to change the AIK path in the script (see step 1 in the Usage section).
2. Create a C:\erd\WinPE directory.
3. Extract the ZFDE_WinPE_Plugin.zip to the C:\erd\WinPE directory. The plugin is available under ZENworks Tools in ZENworks Control Center,
4. Unzip Build_FDE_WinPE_recovery_disk_x86.zip to get the Powershell script file (Build_FDE_WinPE_recovery_disk_x86.ps1). Copy the Powershell script to the C:\erd directory.
5. (Optional) Copy the emergency recovery information (ERI) files that you want included on the Windows PE disk to the C:\erd\WinPE\ERI directory. You must create the ERI directory. If you place the files in a different directory, you will need to change the ERI path in the script (see step 1 in the Usage section).

   If you don't include the ERI files on the disk, you can supply the files via a USB device at the time the disk is used for recovery.

6. Make sure a C:\WinPE directory does not exist before executing the script; this directory is created and used as the build directory.

Usage:

1. If necessary, edit the Powershell script with a text editor to change the following variables:
Variable Default Setting Description $BuildDir C:\WinPE The build directory used to create the Windows PE ISO image.
$Architecture x86 x86 is for Intel and AMD 32-bit processors
amd64 is for Intel and AMD 64-bit processors
ia64 is for Intel Itanium processors
$Language en-us The user locale. Values are standard international language code formats (en-us, de-de, es-es, and so forth).
$KbLayout 0409:00000409 The keyboard layout. The default is en-us. See the Microsoft Go Global Development Center (http://msdn.microsoft.com/en-us/goglobal/bb895996) for layout Ids.
$WAIKInstallation C:\Program Files\Windows AIK The path to the Windows AIK installation.
$ISOLabel Novell_FDE_Recovery_WinPE The volume label assigned to the ISO image.
$PluginDir .\WinPE\EN\files The path to the Full Disk Encryption plugin files. The default uses a relative path from the perspective of the script location.
$ERI_Dir .\ERI The path to the emergency recovery information (ERI) files to include in the ISO image. The default uses a relative path from the perspective of the script location.
2. Run Windows PowerShell with Administrator privileges.
3. Change to the C:\erd directory.
4. Enter the following command to ensure that the Execution Policy for Windows Powershell is set to Unrestricted:
   Set-ExecutionPolicy Unrestricted

   If the Execution Policy is set to Restricted, the script will not run and the following error will be displayed:

   File Build_FDE_WinPE_recovery_disk_x86.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details. At line:1 char:40 + .\Build_FDE_WinPE_recovery_disk_x86.ps1 <<<< + CategoryInfo : NotSpecified: (:) [], PSSecurityException + FullyQualifiedErrorId : RuntimeException
5. Execute the script:
   .\Build_FDE_WinPE_recovery_disk_x86.ps1

   After the script successfully completes, the Novell_FDE_Recovery_WinPE.iso is added to the C:\WinPE directory.

Additional Information:

For information about using the Win PE disk to recover an encrypted device, see the ZENworks 11 Full Disk Encryption Emergency Recovery Reference

AttachmentSize build_fde_winpe_recovery_disk_x86.zip25.59 KB

• Cool Solutions

license:  GNU General Public License

About:

How 'ovpnstatd' works.

ovpnstatd is a status collector daemon for OpenVPN. ovpnstatd can be started either interactively at the console or as a daemon in the background (--daemon).

Use "--help", to get a brief listing of available options.

If started interactively, all connected users and their update-events will be shown on the console-display. This start-mode is merely meant for testing/debugging.

A tcp-port (50505) will be opened, by which a very simple but useful web page can be viewed (http://yourhost:50505). There you get an entry for every OpenVPN-user, whose status-data is available as a result of a connect-event since ovpnstatd's startup. Users who are online, appear as a light-green(ish) entry, disconnected users are shown in grey/white.

The web page will remain empty, as long as no users have connected since startup of ovpnstatd.

The web page is intended for internal (administrator) use only - no "mass media", as ovpnstatd is not a multi-threaded program.

Should ovpnstatd already be running in the background, then you would have to change the port number (--tcp-port <NNNNN>) for your interactive session (if you really want it twice).

Only if started as daemon, ovpnstatd will serve its main purpose, it will collect data of all connect, disconnect, update events, which are reported by any OpenVPN server-process, and write history in csv-format, that can easily be loaded into a database or viewed in a spread-sheet.

In the same time, this data is also written to a FIFO-file "/<status_dir>/send_nsca_data" (/var/run/openvpn/send_nsca_data) in a format suitable for nagios's "send_nsca" utility.

The default location, where collector-data is written, is /srv/www/apps/ovpnstat/datacol - it can be changed with:
"--collect-dir <path-to-your-collector-directory>".

The location where event-data of OpenVPN-hooks is expected, is "/var/run/openvpn". This can be changed with the option:
"--status-dir <path-to-Your-status-directory>".

NOTE: For this to work, you also have to turn on status-logging in OpenVPN config-file(s): "status <path-to-status-data.status>" AND activate the hooks: "client-connect <your-con-script.sh>" and: "client-disconnect <your-dis-script.sh>"

Into the hook-script "your-script.sh" simply place/add the following echo command:

into "client-connect.sh" add the lines
echo -e "OVPN_PID=$PPID\n`env`" \
>/var/run/openvpn/${common_name}.con

into "client-disconnect.sh" add the lines
echo -e "OVPN_PID=$PPID\n`env`" \
>/var/run/openvpn/${common_name}.dis

NOTE: The extension of hook output-files has to be
     .con for client-connect data-files
     .dis for client-disconnect data-files
     .status for status data-files given in OpenVPN config-file
otherwise those files will not be recognized by ovpnstatd.

You can display your favoured icon as a header of the web page.

As default for this, a built-in OpenVPN-icon is displayed.

If you want to replace the default icon in the source (ovpnstatd.h) look for variable "def_web_img64" and substitute its assignment by the output of "base64 -w0 <your-preferred-image>".
But only take tiny images for this !!!

If the TUN/TAP device driver control is not "/dev/net/tun" on your Linux-System, change it with: "--dev-node <Your tun/tap ctrl>"

In case you want to raise the debug-level, use "--debug <N>"
Level 0 = off, 1 = default, 2 = all

Installation:

# assuming that You've downloaded the tar-file to /usr/local/src # proceed als follows: cd /usr/local/src tar -xjvf ovpnstat.tar.bz2 cd ovpnstat make clean make # Now for a test start openvpn status collector daemon interactively : bash ovpnstatd-test.sh # If You got an OpenVPN server up and running on the same host # then You can already take a look on the web-page firefox http://your-host-name:12345/ # But NOTE: ovpnstatd must run on the SAME HOST, where openvpn-server is on # Also note, that collector-data is only written, if the program # is started in the background (--daemon ) . # So to start it for "normal" usage copy file into place: cp init-ovpnstatd /etc/init.d/ovpnstatd cp ovpnstatd /usr/sbin/ovpnstatd # only if You want to send data to Nagios, otherwise leave this away: cp send_nsca.sh # You also will have to create the collector directory # if this location does not meet Your needs, just modify STARTOPTS # in /etc/init.d/ovpnstatd and set --collect-dir to Your favoured mkdir -p /srv/www/apps/ovpnstat/datacol # then start openvpn status daemon /etc/init.d/ovpnstatd start

Special hints:

Regarding Nagios NSCA:

Before you use the Nagios notification script "send_nsca.sh", you need to edit it - change the ip of the Nagios host therein - have a look if all the path-names are suiting your needs - AND install the "send_nsca" binary. It comes with package nagios-nsca-<version>

Once you have installed nagios-nsca on the Nagios server, you may just copy send_nsca from there to your openvpn-server (including its config-file) - that's all it needs.

Also add a Nagios configuration - a hostname entry for your openvpn-server where ovpnstatd will be running (must match exactly the output of 'hostname' and a service entry for each common-name (service_description must match common-name), that you want to monitor passively.

An example of a passive service config also is included here.

Regarding collector data:

The collector data is in csv format which allows you to easily load it into some database for your own web application.

Bugs (and the like creepers):

ovpnstatd is tested valgrind-clean and is running stable since quite a couple of months now on my openvpn-server.

AttachmentSize ovpnstat.tar.bz255.34 KB

• Cool Solutions

download url:  http://download.opensuse.org/repositories/Novell:/NTS/SLE_10/noarch/ license:  GPLv2 home page url:  http://en.opensuse.org/Supportutils Description

Table of Contents
• Update Instructions
• Installation Instructions
• Using Supportconfig
• Reporting Bugs
• Novell Support Advisor

The updateSupportutils command compares the current versions of supportutils and its plugins to those installed on your server. Those that are outdated or missing are automatically downloaded and installed. Only those plugins that apply to your server are installed. The command supports creating a weekly or monthly cron entry to automatically check and update the supportutils package and its plugins. Click here to see a list of the current supportutils and plugin packages. The updateSupportutils command help screen follows:

################################################################ # Supportutils Auto Update Client ################################################################ Usage: updateSupportutils [OPTION] Description Makes sure the supportutils and supportutils plugin packages are installed and current. Options -m Install a monthly cron for updateSupportutils -w Install a weekly cron for updateSupportutils -d Delete all installed cron entries for updateSupportutils -l List all cron entries for updateSupportutils -u Force RPM update on applicable packages -p Exclude supportutils plugin packages -v Verbose mode -h This screen

Note: Detailed system information and logs are collected and organized in a manner that helps reduce service request resolution times. Private system information can be disclosed when using this tool. If this is a concern, please prune private data from the log files. Several startup options are available to exclude more sensitive information. Refer to the supportconfig(8) man page to see these options.

Update Instructions

Run updateSupportutils as root.

If you do not already have the supportutils-plugin-updater package installed, refer to the Installation Instructions below. If your server does not have network connectivity to http://download.opensuse.org, then install using the Option B (Manual) method.
Installation Instructions

Option A (Automated)

1. Download the supportutils-plugin-updater
2. Login as root
3. Install the updater package
   # rpm -Uvh supportutils-plugin-updater-*.noarch.rpm
4. Run updateSupportutils as root
   # updateSupportutils

Option B (Manual)

1. Download the supportutils and any applicable supportutils plugin packages for your server.
2. Login as root
3. Install the supportutils-X.XX-XX.XX.noarch.rpm
   # rpm -Uvh supportutils-X.XX-XX.XX.noarch.rpm
4. Install the supportutils-plugin-*-X.X-X.X.norarch.rpm packages you want
   # rpm -Uvh supportutils-plugin-*-X.X-X.X.norarch.rpm

Using Supportconfig

To upload a supportconfig to Novell, run supportconfig -ur $srnum; where $srnum is your 11 digit service request number. You can also just run supportconfig for local use. By default, supportconfig saves its information in /var/log/nts_hostname_date_time.tbz.

Consider using the Novell Support Advisor to perform an initial analysis of your servers. It will generate an HTML report that links you to Technical Information Documents that directly relate to any server issues identified.

Reporting Bugs

Updates to Supportconfig Version 2.25-320:

• Fixed HA error when cibadmin -Q doesn't connect
• Fixed ldapsearch search on non-default port
• Added systool base output to sysfs.txt
• Added getappcore tool to gather application core files
• Added analyzevmcore tool for kernel core analysis
• Supportconfig includes analyzevmcore files in crash.txt
• /etc/services included in network.txt

Updates to Supportconfig Version 2.25-314:

• Changed to systool for sysfs.txt
• Added local binary list to rpm.txt
• Added nlvm to novell-nss.txt for OES11
• Updated copyright years
• Added curl check for update registrations to update.txt
• Fixed conf file execution in plugins directory
• Added a supportconfig summary in summary.xml
• Added /etc/init.d/halt.local to boot.txt
• Added OPTION_UFILES for fs-files-additional.txt. [see supportconfig.conf(5)]
• Fixed fslist_info order
• Added kdump rpm check for sles11sp1
• Added plugin-icommand to scplugin.rc for internal bash commands

AttachmentSize supportutils-plugin-updater-1.0-19.1.noarch.rpm6.99 KB supportutils-1.20-59.1.noarch.rpm107.48 KB

• Open Enterprise Server Cool Solutions

Vyšlo třetí opravné vydání řady KDE 4.8 a to tedy KDE 4.8.3. Na oficiálních stránkách KDE naleznete oznámení o vydání a dále také seznam změn, ze kterého je vidět, že jde jen o opravy a nikoli o přidávání nových funkcí.

číst dál

license:  GPLv2

The iPrint Backup script is used to backup iPrint to eDirectory and create an XML backup in the /var/opt/novell/iprint/<PSM Name.psm> folder. Any time interval can be used through a crontab entry. One possible use for this script is if your iPrint eDirectory backup is failing periodically. You can find the pattern and identify what could be causing the issue

1. Download iprintbackup.tgz
2. Open a Terminal window and type “su”.
3. Enter root’s password.
4. Extract the script from the tarball.
   #tar –xzvf iprintbackup.tgz
5. Make the script executable and only readable for root.
   #chmod 700 iPrintBackup.sh
6. Open the iPrintBackup.sh script file and fill out the values at the top of the file for the admin eDir username and password
7. Setup crontab for to run 10 minutes after the hour.
   #crontab -e
   Add the line "10 * * * * /[full path to the sript]/XMLBackup.sh
   Save the file (ESC :wq if you are in vi).
8. Your iPrint system should now be backed up.

AttachmentSize iprintbackup.tgz1.11 KB

• Open Enterprise Server Cool Solutions

license:  GPLv2

The Printer Driver Auto Association Script for iPrint allows you to automatically associate a driver to either a specific manufacturer or make/model of a group of printers quickly and easily.

Example of uses:

Example 1:
A company plans on rolling out Windows 7 on workstations and needs drivers associated to each of the 500 printer agents currently found on the print manager. In this situation if the majority of the printers were HP, the Printer Driver Auto Association Script would be able to associate the HP Universal Printer driver to all printers of manufacturer type HP automatically.

Example 2:
A company has 20 printers of a specific model. In this situation, the script would only associate the specific driver chosen to that specific model of printer.

Step #1 - Install and download the latest version of the Printer Driver Auto Association Script utility

Note: Printer Driver Auto Association Script supports OES 2 and 11.
1. Download printer_driver_association-1.1.tgz
2. Open a Terminal window and type “su”.
3. Enter root’s password.
4. Extract the script from the tarball.
   #tar –xzvf printer_driver_association-1.1.tgz
5. cd to the PrinterDriverAssociations folder.
   #cd PrinterDriverAssociations
6. Make the script executable.
   #chmod 755 PrinterDriverAssociation-1.1.sh
Step #2 - Run the Printer Driver Auto Association Script utility

Option A: Generate a file containing the list of printers matching a specific manufacturer or model

1. On the terminal run the Printer Driver Auto Association Script to generate just the file.
   #PrinterDriverAssociation-1.1.sh -g
2. This will create a file in the current working directory containing the printers identified during the script execution.
   A log file named associations.log will be generated in the /var/opt/novell/log/iprint/ directory.
Option B: Generate the printers file and auto associate the chosen driver to the printers found in the file.
1. On the terminal run the Printer Driver Auto Association Script to generate just the file.
   #PrinterDriverAssociation-1.1.sh -f <filename.txt> -g
2. This will create a file in the current working directory containing the printers identified during the script execution. It will then execute the file and associate the driver chosen during the script execution.
   A log file named associations.log will be generated in the /var/opt/novell/log/iprint/ directory.
Note: Using a –h will display the help menu.

AttachmentSize printer_driver_association-1.1.tgz4.89 KB

• Open Enterprise Server Cool Solutions

SuSE/OpenSUSE používám již řadu let a když jsem si pořídil neťas, tak tam také pochodovalo OpenSUSE 12.1. Dlouho jsem probíral, až jsem vybral ACER Aspire One 722. Důvodů bylo několik: za prvé se dal koupit bez Windows, za druhé se vešel do jednoho a půl kila a za třetí, a to hlavně, měl deklarovanou slušnou výdrž - prostě aby pár hodin s přehledem vydržel.

číst dál

license:  Free Without Warranty home page url:  http://jlodom.org

Jason Blackett posted instructions for creating an OS X package to install the ZENworks Adaptive Agent at http://www.novell.com/communities/node/13558/building-mac-os-x-package-install-zenworks-112-adaptive-agent

My tool refines Jason's instructions in two ways:

1. It uses WhiteBox software's Packages application, which is much easier to download and install than XCode / PackageMaker.
2. Most of the work is done for you -- You only need to install Packages, download your own copy of the Adaptive Agent binary installer, and then run the "Build" command from packages. Voila! Instant installer.

Everything you need, including more detailed instructions, is included with the zip file attached to this posting. Happy deployment!

AttachmentSize zaa_osx_package.zip73.85 KB

• Cool Solutions

license:  Free Without Warranty home page url:  http://jlodom.org

ZENworks understands icons in png and ico format. OS X uses icns format for its icons. I have created a clickable script using native OS X tools and a compiled copy of the open source png2ico tool ( borrowed from http://harvey.nu/installers ) that will bluntly create png and ico versions of every icon associated with the OS X application that you select. These files can then be uploaded to ZENworks Configuration Management and associated with OS X bundles, where they will then show up in the ZENworks Window.

The file included here is a package installer that will install the necessary files to /Applications/ZENWorks Cool Tools/zenicon/ . The readme.txt in that folder has further details on usage.

Please let me know if you find this tool useful, and how it might be improved.

AttachmentSize zenicon.zip68.83 KB

• Cool Solutions

Taky vám pořád v možnostech zobrazení Krusaderu chybí náhledy obrázků (thumbnails)?

číst dál

license:  MPL (Mozilla Public License) Introduction

The Generic File Driver is similar to the Text Driver shipped with IDM, but has more options, and has the capability to read virtually any file type. Out of the box, the following file types are supported: XML, CSV and XLS (the latter using POI from Apache).

The original version I wrote in 2007 is located at http://www.novell.com/coolsolutions/tools/18671.html. This update comes with an IDM 4 package making the installation simpler and has some new features and fixes.
See the referenced version for a list of the old features.

New features and fixes

version 0.4, 24-APR-2012

• Shim bug: Fixed an issue with the driver schema (appeared to be hard coded).
• Shim feature: Added beta support for query back. Query back only supported on publisher channel (when reading in a file). Feedback welcome.
• Package bug: Fixed an issue that caused the driver configuration not to be imported when the package was imported.
• Package bug: Changed creation policy from validating the Given Name to validating the Surname.
• Package feature: Added package 'Delimited Text Driver Password Synchronization Package' as an optional package for this driver.
• Package feature: Added remote loader prompts to the package.

version 0.3, 12-OCT-2011

• Shim feature: automatic association and src-dn calculation (using ecmascript in the driver configuration). No longer need for style sheets for just creating association and src-dn values. The driver shim now does this for you.
• Shim bug: fixed missing remove-all-values on the publisher documents.
• Shim feature: added the ability (csv output files) to flush the file buffer after every record written (useful for when you are developing/testing your driver).
• Shim feature: when receiving a modify event on the subscriber channel, the shim will query back for all missing attribute values in order to be able to write a complete record (no need for a stylesheet to query for missing attributes and keeping this stylesheet in sync with the schema).
• Shim bug/feature: the subscriber channel now fully support add, modify and instance events. Instance and add events are assumed to contain all data and do not perform a query back. Only the modify event performs a query back

Installation

The attached zip file (GenFileDriver_0_4.zip) contains 2 jar files. One is the package, one is the shim.
Shim: GenFileDriverShim_0.4.jar
Copy the shim to you eDirectory server (DirXML's classes folder). If you want to use XLS support, also download poi from Apache. Restart eDirectory after this.
Note: if you have a previous version, be sure to delete that jar.
Package: SVCGENFILEB_0.0.4.jar
Import this package into your designer project. Drag and drop the "Delimited Text" driver that is located under "Tools" and select the "Generic File Base" package, answering all the questions as needed.
From this point on, you can use and modify it as any other driver.

Policies

This driver only has 3 policies; all of them on the publisher channel. If required, you could add the password policies as available from the standard text driver (by creating your own copy from Novell's package and adding this to the driver).
SVCGENFILEB-pub-mp
Match on Internet Email Address if any available.
SVCGENFILEB-pub-cp
Checks for mandatory attributes:
Surname: required due to eDir constraints
Internet Email Address: required due to use in matching policy
SVCGENFILEB-pub-pp
Placement based on a driverset GCV (idv.dit.data.users).

AttachmentSize genericfiledriver_0_4.zip148.83 KB

• Cool Solutions

license:  Free

Nagios is an open source tool that can be installed on SLES/OES that allows you to monitor your network and servers. The plugins attached are specifically written to monitor some of the functions of Open Enterprise Server and eDirectory, so you can remotely see how your server is performing. A big thanks to Novell Technical Services in Germany who contributed these scripts.

The wonderful thing about Nagios, is anyone with some scripting ability can write additional monitoring plugins. The intent here is that this will start as a good base of plugins and that other administrators would contribute additional plugins.

Send me a note if you have an additional plugin you have written to monitor SLES or OES and I'll update this thread with the additions. You can also post it separately on cool solutions as a tool and earn additional points!

AttachmentSize nagios-plugins_and_docs.zip698.68 KB

• Open Enterprise Server Cool Solutions

license:  Free Without Warranty home page url:  http://jlodom.org

The ZENworks agent on OS X workstations includes the ZENworks Window (Known to pre-ZEN-10 greybeards as NAL for "Novell Application Launcher"). However, unlike the Windows agent, the Mac agent does not include an application that can start the Launcher in a GUI way (either by double-clicking or as a Startup item). This little package provides that GUI.

The "application" is just a short compiled AppleScript with the ZEN icon. It requires that the ZENWorks OS X agent already be installed. The script is almost identical to the Launcher script for Linux, with some minor alterations.

There are four files included in NALmac.zip:

1. This readme.txt
2. "ZENworks Window.app" which is the compiled script, ready to run.
3. NALmac_script.txt which contains the simple AppleScript code, for those who might like to improve on it (which would not be hard).
4. NALmac.pkg, which is a simple package installer to put a copy of the application in /Applications/ZENWorks Cool Tools/ if you want to deploy it en masse.

Please let me know about your experience with this little tool, and how it might be improved.

AttachmentSize nalmac.zip59.88 KB

• Cool Solutions

license:  Free without Warranty home page url:  http://jlodom.org

The ZENworks OS X agent (ZAC) is based on the ZENworks Unix agent. By default, both of these agents only grant SuperUser rights to the "root" user, which is a standard best practice in the Unix world. However, on OS X the "root" user is disabled by default, and best practice for OS X is to do everything with another local administrative user instead of enabling or using root.

So, whose best practice do you use? This script furthers OS X best practices by granting a local administrative user SuperUser rights in ZAC without permanently enabling root or requiring manual intervention. Once the local admin has SuperUser rights to ZAC, any other ZAC user changes can be done by this administrator and we never have to think about "root" again.

The script works by temporarily enabling root using OS X's "dsenableroot" command, using "Expect" to SSH into the workstation from itself, running the appropriate ZAC commands to grant privileges, and ends by running dsenableroot again -- this time to DISable the root user (including wiping root's temporary password).

Script syntax is very simple:
/path/to/script/zacosxadmin.expect adminusername adminuserpassword newrootpassword
and the script is suitable for deploying from Terminal, ZENWorks itself, Apple Remote Desktop, or whatever other non-Novell Mac deployment system you are going to be replacing with ZEN :) .

More documentation is in the script's own comments. I have tested it on OS X 10.5, and it should be thoroughly forward-compatible. Please let me know what your experience is with it, whether you find it useful, and how it might be improved.

AttachmentSize zacosxadmin.zip1.67 KB

• Cool Solutions

license:  Free

download url: http://brummelhook.com/download/pwfilter_inf.zip
home page url: http://brummelhook.com/dirxml

The IDM AD driver requires a filter DLL to be installed on all DCs for password synchronization. Unfortunately, it seems as if the IDM setup does not always update a previously installed version of pwfilter.dll (and associated files) properly.

This INF installer can be used to update those files so they will be used after the next reboot:

1. place setup_pwfilter.inf in the C:\Novell\IDM_PassSync folder on the machine where you installed the IDM AD driver
2. right-click on setup_pwfilter.inf and choose "Install"
3. Reboot
4. verify file versions of pwfilter.dll and psevent.dll in your system32 folder

Many thanks to Alex McHugh for adding x64 support and fixing some bugs!

• Cool Solutions

Ačkoliv jsem vyrostl na Windows (a začínal jsem opravdu ještě na 3.11...), s Linuxem jsem začal "koketovat" asi před pěti lety. Vyzkoušel jsem ty nejběžnější verze, ale nejvíc mě vyhovovalo sestavení SUSE. I když tam bylo stále mnoho věcí, které byly pro mě příliš složité, zejména v suse 11.

číst dál

Ja vim, ze tento portal je hlavne pro uzivatele openSUSE, ale po 4 letech pouzivani openSUSE a po celkem znacnem zklamani s soucasnym stavem distribuce openSUSE 12.1 (hlavne mam na mysli neaktualni klicove aplikace v repozitarich a radu dalsich nedotazenosti v KDE a KDE aplikacich) jsem se rozhodl otestovat Kubuntu 12.04 beta2.

číst dál

Pokud jste dnes dělali aktualizaci systému, mohli jste zjistit, že vyšlo další vydání KDE řady 4.8, a to konkrétně KDE SC 4.8.2.

číst dál

Jak uvádím v nadpisu, kancelářský balík LibreOffice (ve verzi 3.5.2) už je v oficiálním repozitáři. Zatím pouze v Unstable větvi, ale kdo chce vyzkoušet openSUSE verzi místo té "nativní", má nyní usnadněnou práci.

číst dál

license:  Free

This is a Perl-coded script designed to backup eDirectory on Linux or Solaris. eDirectory 8.7.x and 8.8 along with NICI 2.6.x and 2.7 currently work and are tested on Linux and Solaris. To run the script save it to a box with eDirectory on it and make the script executable. The script will automatically run with Perl when it is run directly. Perl comes, by default, on all Unix and Linux distributions. The script will run anywhere Perl is though it is not made to do anything properly on other platforms.

Update: 2012 Mar 22 - Fixes a couple of potential issues that have come up over the past couple years.

Update: 2007 Mar 03 - Now backs up vardir instead of dibdir only. For 8.8 it also backs up dibdir if it is not contained in vardir for large distributed-filesystem environments.

The script has a few options that can be passed in for scriptability without prompts. The info from ndsrc.pl -h follows:

Usage:

./ndsrc.pl -h   #Show help information. This info here. ./ndsrc.pl -p    /tmp/backup/path/goes/here ./ndsrc.pl -c  /etc/nds/conf/file/nds.conf[,/etc/other/conf/file/nds.conf] ./ndsrc.pl -d  /etc/opt/novell/eDirectory/conf/.edir/ ./ndsrc.pl -s   #Force through the reminders that are defaults.

The -p option lets you specify where to put the destination TAR (Tape ARchive) files. This defaults to /root for security reasons. On Solaris you will want to create and secure this directory if it does not exist by default.

The -c option specifies a configuration (nds.conf) file specifically. This is useful for eDirectory 8.8 where multiple instances exist and need to be backed up in a scripted fashion (weekly backups of the entire DIB, for example).

The -d option specifies the directory where multiple configuration files exist. By default this is the /etc/opt/novell/eDirectory/conf/.edir/ directory. Having this configurable allows the script to be used for non-root installations of eDirectory. Non-root installations are installed all to one location, like a user's home directory.

The -s option skips through the first prompt telling the user that the DS instance that is backed up will be shutdown for the backup to be properly taken. Use this whenever the script is called from other scripts where interactivity is not an option. It can also be used to prevent one more check that may be annoying.

To run this script with eDirectory 8.8 be sure you have run the ndspath command. Without this the script will fail because it cannot find ndsmanage. This goes for eDirectory installed as root or non-root. As long as ndsmanage can be called without the absolute path the script will work.

The script has many lines of comments at the beginning regarding the scripts operation. Read these before using the script. Also you should try this out on your own and understand how things work before making this backup your DS nightly. Failing to do so could leave your DS stopped when it should have been restarted. The script performs no checks for adequate space and each backup is made to a new file so running this regularly will, eventually, fill your hard drive.

At the end of each run of the script a return value is sent back to the prompt for interpretation. A 0 means there were no fatal errors, a 1 means there was a fatal error. As other commands are made by the script the return values of those calls is included in the log which is output to the screen (via STDERR). That can be redirected to /dev/null (./ndsrc.pl -s 2>/dev/null) or it can be saved to a file for further analysis and interpretation (mail it to yourself, for example). The logging is fairly extensive and very helpful for troubleshooting.

The ability to backup other *nix's may come as I am able to find and test them (AIX is probably next). Comments/critiques/questions appreciated. The source is highly-commented and that is for the good of us all.

AttachmentSize ndsrc.zip11.11 KB

• Cool Solutions