Active Directory contains a very useful feature which allows for Administrators to automatically deploy software to machines or users automatically when the machine is booted or a user logs on. This document assumes you will be deploying software to a set of machines in which the user does not have local admin rights, so it will focus on the process to deploy to the computers via the Computer Configuration GPO setting.
Author Archives: admin
MSI e Windows Installer
6 de Março de 2008 – 15:24
Para fazer uma instalação silenciosa de um .msi pode usar a sintaxe:Â
msiexec /i filename /q
FreeTDS
4 de Março de 2008 – 20:20
FreeTDS is a set of libraries for Unix and Linux that allows your programs to natively talk to Microsoft SQL Server and Sybase databases.
Technically speaking, FreeTDS is an open source implementation of the TDS (Tabular Data Stream) protocol used by these databases for their own clients. It supports many different flavors of the protocol and three APIs to access it. Additionally FreeTDS works with other software such as Perl and PHP, providing access from those languages as well.
If you are looking for a Java implementation, we refer you to the jTDS project on SourceForge.
FreeTDS has many possible uses. It has been used by Unix/Linux webservers to present data stored in SQL Server to the web, to port SQL Server database code from NT to Unix, to import data into SQL Server from a Unix source, and to provide database access on platforms (such as realtime systems) that have no native drivers.
The FreeTDS C libraries are available under the terms of the GNU LGPL license, consult the COPYING.LIB file in the distribution for details.
User Profile Hive Cleanup
4 de Março de 2008 – 20:17
O serviço User Profile Hive Cleanup ajuda a assegurar que as sessões de usuário serão encerradas completamente quando o usuário fizer logoff. Os aplicativos e os processos do sistema mantêm, ocasionalmente, conexões com chaves do Registro no perfil do usuário depois que o usuário faz logoff. Isso faz com que a sessão do usuário não seja encerrada completamente, causando problemas durante a utilização de perfis móveis de usuários, em um ambiente de servidor, ou de perfis bloqueados implementados através do Shared Computer Toolkit para Windows XP.
read more
SMTP error codes
21 de Fevereiro de 2008 – 11:02
SMTP is responsible for sending out your messages. So if you get SMTP error message, it means your e-mails were not send. It is very important you to understand why this has happened so that you can fix the problem. All SMTP codes consist of three digits, for example, 550, 221, 354, etc. Not all of them mean some type of error. In order to understand how these codes work, you have to know that each digit (the first, the second and the third) have there own meaning.
How to install KDE on Ubuntu
19 de Fevereiro de 2008 – 2:49
Ubuntu’s default desktop environment is Gnome. Sometimes people using Ubuntu want to try out KDE as well, though.
Warning: having KDE and Gnome together means you’ll have cluttered application menus full of KDE applications and Gnome applications. You may also run into some other cosmetic problems (the KDE QT look taking over some of your Gnome themes, a hidden file on your desktop that keeps appearing in Gnome after you’ve just logged out of KDE). One of the most common problems is the new desktop environment “taking over” the boot splash screen. Here are some instructions to fix that problem.
Even though these instructions are for KDE, the same principle applies for adding Gnome to Kubuntu or XFCE to Kubuntu or Ubuntu. Basically, you install the desktop environment, log out, and choose the desktop environment.
Note: Some people may tell you to install KDE using Synaptic Package Manager or apt-get. Using aptitude instead will make KDE easier to remove later if you wish to do so.
Paste this command in the terminal:
sudo aptitude update && sudo aptitude install kubuntu-desktop
Free Image Hosting at www.ImageShack.us
During the installation process, you should be asked whether you want to use KDM or GDM as your default display manager. If you think you’ll use KDE more frequently, make KDM your default. If you think you’ll use Gnome more frequently, keep GDM as your default.
The default can always be changed later by modifying the /etc/X11/default-display-manager file. For KDM, the file should read /usr/bin/kdm; for GDM, the file should read /usr/sbin/gdm
Free Image Hosting at www.ImageShack.us
When KDE is done installing, log out.
Free Image Hosting at www.ImageShack.us
If you’re using 6.06 or later, once you get to the login screen, click on Options and then Select Session.
In older versions of Ubuntu (5.10 or earlier), you would have a separate Session button instead of drilling down to Session from Options.
Free Image Hosting at www.ImageShack.us
In the Sessions dialogue, select KDE and then Change Session.
Free Image Hosting at www.ImageShack.us
Finally, before you log back in again, decide whether you want to change to KDE just for this session or if you want to make KDE your default desktop environment.
Then, log back in, and you should be using KDE.
To switch back to Gnome, just log out and select Gnome from the session menu.
If you later decide you don’t want KDE any more, go back to the terminal and paste in
sudo aptitude remove kubuntu-desktop
Source: http://www.psychocats.net/ubuntu/kde
Fujitsu Primergy RX300 Server
18 de Fevereiro de 2008 – 22:44
The Fujitsu Primergy RX300 Server offers great expandability, dual Xeon processors and high-availability through memory scrubbing plus Chipkill, hot spare memory and hot-plug/redundant power supplies and fans.
* Processor: 1-2 Intel Xeon 533 MHz FSB 2.40 / 2.66 / 2.80 / 3.06 GHz
* Memory: 512 MB to 12 GB ECC DDR-SDRAM memory
* Disk: 6 x 18 GB, 36 GB, 73 GB or 146 GB Ultra320 SCSI hot-plug disks
* Memory scrubbing, Chipkill, hot-spare memory option
* Max. 876 GB disk storage
* 2 x Ultra320 SCSI with RAID-0,1,10; 2 x 10/100/1000 Mbit/s Ethernet LAN
link:
http://www.fujitsu-siemens.com/products/standard_servers/benchmarks/primergy_rx300s3.html
http://www.b2net.co.uk/primergy/fujitsu_primergy_rx300_server.htmÂ
Unidade de Medida de Racks
6 de Fevereiro de 2008 – 18:08
“Rack Unit” é a unidade de medida utilizada para descrever a altura de servidores, switches e outros dispositivos montados em racks de 19 polegadas.
Cada “rack unit” equivale a 44.45 mm (1.75″).
As medidas nesta unidade são representadas pelo número equivalente seguido da letra “U”, no formato “1U”, “2U”, “3U” e assim por diante. Algumas vezes a representação também é feita no formato “1RU”.
Virtual Floppy Drive 2.1
27 de Janeiro de 2008 – 20:39
This is a virtual floppy drive for Windows NT / 2000 / XP (works also on 2003, it seems).
Note !!! This version works only on 32 bit systems !!!
See technical info on 64 bit compilation.
You can mount a floppy image file as a virtual floppy drive and directly access the contents — view, edit, rename, delete or create files on a virtual floppy, format a virtual floppy, launch a program on a virtual floppy… almost anything you can do with a real floppy.
Homepage: http://chitchat.at.infoseek.co.jp/vmware/vfd.html#downloadÂ
Homepage Download: http://chitchat.at.infoseek.co.jp/vmware/vfd21-050404.zip
Local Download: vfd21-050404.zip
DBCC SHRINKFILE
8 de Janeiro de 2008 – 13:11
Como usar o comando DBCC SHRINKFILE para reduzir o tamanho do log de transacções de uma base de dados SQL Server 2005
In SQL Server 2005, a shrink operation (DBCC SHRINKFILE) tries to shrink the specified transaction log file to the requested size immediately. To shrink the transaction log file manually under the full recovery model, first back up the transaction log file. Then, use the DBCC SHRINKFILE statement to shrink the transaction log file.
Typically, shrinking the transaction log file in SQL Server 2005 is faster than shrinking the transaction log file in SQL Server 2000. The reason is that the SQL Server 2005 log manager creates or reuses inactive virtual log files by following the physical disk storage order. Therefore, the inactive part of the transaction log file is usually at the end of the file.
For example, the transaction log file may have 100 virtual log files, and only 2 virtual log files are used. SQL Server 2000 may store the first used virtual log file at the start of the transaction log file and the second used virtual log file in the middle of the transaction log file. To shrink the transaction log file to only 2 virtual log files, SQL Server fills the remaining part of the second virtual log file by using dummy log entries. SQL Server moves the start of the logical log to the next available virtual log file that is specified by the log manager. The log manager may create a virtual log file in the middle of the transaction log file just ahead of the last active virtual log file. In that case, you have to use multiple log backup operations and multiple shrink operations to successfully shrink the transaction log file to 2 virtual log files. In the worst case of this example, you may have to use 50 log backup operations and 50 shrink operations to successfully shrink the transaction log file to 2 virtual log files.
However, in SQL Server 2005, you can perform one DBCC SHRINKFILE statement to shrink the transaction log file immediately to 2 virtual log files. You can do this because the SQL Server 2005 log manager creates 2 virtual log files by following the physical disk storage order. Both of these virtual log files are at the start of the transaction log file.
When you try to shrink a transaction log file that has little free space in SQL Server 2005, you may have to perform an additional log backup operation. The additional log backup operation truncates the transaction log file to a smaller size. This log backup operation is in addition to the three steps that you perform to shrink the transaction log file in SQL Server 2000. For more information, see the Microsoft Knowledge Base article that is mentioned in the “Introduction” section. To shrink a transaction log file that has little free space in SQL Server 2005, follow these steps:
1. Back up the transaction log file to make most of the active virtual log files inactive. Therefore, the inactive virtual log files can be removed in a later step. To do this, run a Transact-SQL statement that is similar to the following Transact-SQL statement. BACKUP LOG
Note In this statement,
For example, run the following Transact-SQL statement. BACKUP LOG TestDB TO DISK=’C:\TestDB1.bak’
Â
2. Shrink the transaction log file. To do this, run a Transact-SQL statement that is similar to the following Transact-SQL statement. DBCC SHRINKFILE (
Note In this statement,
3. If the DBCC SHRINKFILE statement does not shrink the transaction log file to the target size, run the BACKUP LOG statement that is mentioned in step 1 to make more of the virtual log files inactive.
4. Run the DBCC SHRINKFILE statement that is mentioned in step 2. After this operation, the transaction log file should be similar to the target size.
In summary, the log manager’s algorithm for picking up the next virtual log file changed in SQL Server 2005. Therefore, shrinking the transaction log file in SQL Server 2005 may differ from shrinking the transaction log file in SQL Server 2000:
- If a log file has lots of free space, shrinking the transaction log file in SQL Server 2005 is faster than shrinking the transaction log file in SQL Server 2000.
- If a log file has no free space, shrinking the transaction log file in SQL Server 2005 is the same as shrinking the transaction log file in SQL Server 2000.
- If a log file has little free space, you may have to perform an additional log backup operation in SQL Server 2005 than you have to perform in SQL Server 2000.
REFERENCES
For more information, see the following topics in SQL Server 2005 Books Online:• Shrinking the transaction log
• DBCC SHRINKFILE (Transact-SQL)
• Truncating the transaction log
Home