How to silently install/uninstall IrfanView?

A: Usually, you can download the ZIP version of IrfanView and Plugins and deploy the files.
Self install versions have special start options for silent install (examples, version 4.20):
1) IrfanView:

iview420_setup.exe /silent /folder="c:\test folder\irfanview" iview420_setup.exe /silent /folder="c:\test folder\irfanview" /desktop=1 /thumbs=1 /group=1 /allusers=0 /assoc=1 /ini="%APPDATA%\irfanview" iview420_setup.exe /silent /folder="c:\test folder\irfanview" /ini="c:\temp" Options: folder:     destination folder; if not indicated: old IrfanView folder is used, if not found, the "Program Files" folder is used desktop:  create desktop shortcut; 0 = no, 1 = yes (default: 0) thumbs:   create desktop shortcut for thumbnails; 0 = no, 1 = yes (default: 0) group:     create group in Start Menu; 0 = no, 1 = yes (default: 0) allusers:  desktop/group links are for all users; 0 = current user, 1 = all users assoc:     if used, set file associations; 0 = none, 1 = images only, 2 = select all (default: 0) assocallusers:  if used, set associations for all users (Windows XP only) ini:      if used, set custom INI file folder (system environment variables are allowed)

2) PlugIns:

irfanview_plugins_420_setup.exe /silent

3) Uninstall:

iv_uninstall.exe /silent

Netowrk Drivers for HP compaq dc5800 Desktop PCs for all OSs

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18719&keyword=%22intel+82566dm-2+%22&lang=eng

How To Auto-Clean Windows Vista With CCleaner

From http://maketecheasier.com/auto-clean-windows-vista-by-scheduling-ccleaner/2009/02/02/

If you’re not familiar with everyone’s favourite system cleaner, CCleaner, it’s a freeware system optimization, privacy and cleaning tool.  This application does a very nice job at cleaning up after you, assuming that you actually remember to run it. In today’s fast-paced world, many of us don’t have the time or capacity it takes to remember all of the little things that have to get done.  System maintenance is no exception.
In this tutorial, I’m going to walk you through setting up CCleaner to automatically run on a schedule in Windows Vista so that you can simply set it and forget it.

Configure Your Options

Making sure that you have set the correct options inside of CCleaner is very important if you plan to automate it. For example, what if you decide to run it every night and you have it set to clean out your recent documents or cookies. That could become very frustrating in a very short time.
Start by opening CCleaner and selecting the options you want in the Windows Cleaner section that opens by default. I can’t tell you what settings to use because everyone will have different needs. All I can tell you is that you need to think about each option carefully and consider that possible outcomes.

The next piece that you’ll want to look at is the Advanced Options. Click on the Options button in the lower left corner of the window, then click Advanced. Make sure that Save all settings to INI file is checked.

Create the Scheduled Task

Open up the Start menu in Windows, then go to All Programs –> Accessories –> System Tools –> Task Scheduler. If Windows prompts you to tell you that it needs your permission to continue, simply click the Continue button.
Once the task schedule window is open, click on Create Basic Task. A new wizard will open to help you through the process.  Give your task a meaningful name and description. I chose “System Cleanup” for the name and “This task launches CCleaner to perform a system cleanup on a regular basis.” Click Next.


The Task Trigger window is where you determine what causes the task to run. In our case, we want a time period to be the trigger. I personally find weekly to be sufficient, but you can choose daily or monthly depending on your individual needs. After you select your trigger, click Next.

Now the scheduler needs you to get a little more granular by selecting the day of the week and the time that the task will run.  This choice is very important. For example, if you turn your PC off at night, then you don’t want to run the task in the middle of the night. You also don’t want the task to run when you are likely to be in the middle of using the computer. Once you decide on the finer details, click Next.

Now it’s time to tell the scheduler just exactly what you want it to do. It defaults to Start a program, so just click Next. Click the Browse button and locate the CCleaner.exe program file. The default location is:

C:Program FilesCCleanerCCleaner.exe

In the Add arguments section, add the /AUTO switch. This tells CCleaner to run automatically without waiting for user input.  Click Next to get to the Summary screen. Check the box next to Open the Properties Dialog for this task when I click Finish and click the Finish button.

In the Properties window, check the box next to Run with the highest privileges. This is required so that the task can run without prompting you for administrator privileges. Next click on the Conditions tab and check the box next to Wake the computer to run this task. This will bring your computer out of sleep mode in the event that the power saver settings have put it to sleep.  Click Ok to finish the process.

You can try out the task to make sure everything was configured properly by right-clicking on your new task and selecting Run.

If everything is ok, you should see the CCleaner icon appear in your system tray.
You can get more info about CCleaner from the CCleaner website, or from our handy walkthrough.

Norm is a a Canadian IT professional with 12 years of experience under his belt as a Technology Architect, Microsoft Certified Application Developer and as an Analyst. He has written numerous articles for multiple technology blogs, in addition to his own blog http://www.geekeleet.com.

To automatically shutdown after cleanup, use the following command:

"C:\Program Files\CCleaner\CCleaner.exe" /AUTO /SHUTDOWN

Converting Additional Domain Controller into PDC by transferring FSMO Roles

Converting Additional Domain Controller into PDC FSMO Roles when the PDC is available

Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory.
In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC.
Moving the FSMO roles while both the original FSMO role holder and the future FSMO role holder are online and operational is called Transferring, and is described in this article.
The transfer of an FSMO role is the suggested form of moving a FSMO role between domain controllers and can be initiated by the administrator or by demoting a domain controller. However, the transfer process is not initiated automatically by the operating system, for example a server in a shut-down state. FSMO roles are not automatically relocated during the shutdown process - this must be considered when shutting down a domain controller that has an FSMO role for maintenance, for example.
In a graceful transfer of an FSMO role between two domain controllers, a synchronization of the data that is maintained by the FSMO role owner to the server receiving the FSMO role is performed prior to transferring the role to ensure that any changes have been recorded before the role change.
However, when the original FSMO role holder went offline or became non operational for a long period of time, the administrator might consider moving the FSMO role from the original, non-operational holder, to a different DC. The process of moving the FSMO role from a non-operational role holder to a different DC is called Seizing, and is described in the Seizing FSMO Roles article.
You can transfer FSMO roles by using the Ntdsutil.exe command-line utility or by using an MMC snap-in tool. Depending on the FSMO role that you want to transfer, you can use one of the following three MMC snap-in tools:

• Active Directory Schema snap-in
• Active Directory Domains and Trusts snap-in
• Active Directory Users and Computers snap-in

To transfer the FSMO role the administrator must be a member of the following group:

FSMO Role	Administrator must be a member of
Schema	Schema Admins
Domain Naming	Enterprise Admins
RID	Domain Admins
PDC Emulator
Infrastructure

Transferring the RID Master, PDC Emulator, and Infrastructure Masters via GUI
To Transfer the Domain-Specific RID Master, PDC Emulator, and Infrastructure Master FSMO Roles:

1. Open the Active Directory Users and Computers snap-in from the Administrative Tools folder.
2. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Users and Computers and press Connect to Domain Controller.
3. Select the domain controller that will be the new role holder, the target, and press OK.
4. Right-click the Active Directory Users and Computers icon again and press Operation Masters.
5. Select the appropriate tab for the role you wish to transfer and press the Change button.
6. Press OK to confirm the change.
7. Press OK all the way out.

Transferring the Domain Naming Master via GUI
To Transfer the Domain Naming Master Role:

1. Open the Active Directory Domains and Trusts snap-in from the Administrative Tools folder.
2. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Domains and Trusts and press Connect to Domain Controller.
3. Select the domain controller that will be the new role holder and press OK.
4. Right-click the Active Directory Domains and Trusts icon again and press Operation Masters.
5. Press the Change button.
6. Press OK to confirm the change.
7. Press OK all the way out.

Transferring the Schema Master via GUI

To Transfer the Schema Master Role:

1. Register the Schmmgmt.dll library by pressing Start > RUN and typing:

regsvr32 schmmgmt.dll

1. Press OK. You should receive a success confirmation.
2. From the Run command open an MMC Console by typing MMC.
3. On the Console menu, press Add/Remove Snap-in.
4. Press Add. Select Active Directory Schema.
5. Press Add and press Close. Press OK.
6. If you are NOT logged onto the target domain controller, in the snap-in, right-click the Active Directory Schema icon in the Console Root and press Change Domain Controller.
7. Press Specify .... and type the name of the new role holder. Press OK.
8. Right-click right-click the Active Directory Schema icon again and press Operation Masters.
9. Press the Change button.
10. Press OK all the way out.

Transferring the FSMO Roles via Ntdsutil
To transfer the FSMO roles from the Ntdsutil command:
Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.

1. On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\WINDOWS>ntdsutil
ntdsutil:

1. Type roles, and then press ENTER.

ntdsutil: roles
fsmo maintenance:

Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER.

1. Type connections, and then press ENTER.

fsmo maintenance: connections
server connections:

1. Type connect to server , where is the name of the server you want to use, and then press ENTER.

server connections: connect to server server100
Binding to server100 ...
Connected to server100 using credentials of locally logged on user.
server connections:

1. At the server connections: prompt, type q, and then press ENTER again.

server connections: q
fsmo maintenance:

1. Type transfer . where is the role you want to transfer.

For example, to transfer the RID Master role, you would type transfer rid master:
Options are:

Transfer domain naming master
Transfer infrastructure master
Transfer PDC
Transfer RID master
Transfer schema master

1. You will receive a warning window asking if you want to perform the transfer. Click on Yes.
2. After you transfer the roles, type q and press ENTER until you quit Ntdsutil.exe.
3. Restart the server and make sure you update your backup.

Converting Additional Domain Controller into PDC by Seizing FSMO Roles

Converting Additional Domain Controller into PDC When PDC is not available or has crashed by Seizing FSMO Roles


Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory.
The five FSMO roles are:

• Schema master - Forest-wide and one per forest.
• Domain naming master - Forest-wide and one per forest.
• RID master - Domain-specific and one for each domain.
• PDC - PDC Emulator is domain-specific and one for each domain.
• Infrastructure master - Domain-specific and one for each domain.

In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC.
Moving the FSMO roles while both the original FSMO role holder and the future FSMO role holder are online and operational is called Transferring, and is described in the Transferring FSMO Roles article.
However, when the original FSMO role holder went offline or became non operational for a long period of time, the administrator might consider moving the FSMO role from the original, non-operational holder, to a different DC. The process of moving the FSMO role from a non-operational role holder to a different DC is called Seizing, and is described in this article.
If a DC holding a FSMO role fails, the best thing to do is to try and get the server online again. Since none of the FSMO roles are immediately critical (well, almost none, the loss of the PDC Emulator FSMO role might become a problem unless you fix it in a reasonable amount of time), so it is not a problem to them to be unavailable for hours or even days.
If a DC becomes unreliable, try to get it back on line, and transfer the FSMO roles to a reliable computer. Administrators should use extreme caution in seizing FSMO roles. This operation, in most cases, should be performed only if the original FSMO role owner will not be brought back into the environment. Only seize a FSMO role if absolutely necessary when the original role holder is not connected to the network.
What will happen if you do not perform the seize in time? This table has the info:

FSMO Role	Loss implications
Schema	The schema cannot be extended. However, in the short term no one will notice a missing Schema Master unless you plan a schema upgrade during that time.
Domain Naming	Unless you are going to run DCPROMO, then you will not miss this FSMO role.
RID	Chances are good that the existing DCs will have enough unused RIDs to last some time, unless you're building hundreds of users or computer object per week.
PDC Emulator	Will be missed soon. NT 4.0 BDCs will not be able to replicate, there will be no time synchronization in the domain, you will probably not be able to change or troubleshoot group policies and password changes will become a problem.
Infrastructure	Group memberships may be incomplete. If you only have one domain, then there will be no impact.

Important: If the RID, Schema, or Domain Naming FSMOs are seized, then the original domain controller must not be activated in the forest again. It is necessary to reinstall Windows if these servers are to be used again.
The following table summarizes the FSMO seizing restrictions:

FSMO Role	Restrictions
Schema	Original must be reinstalled
Domain Naming
RID
PDC Emulator	Can transfer back to original
Infrastructure

Another consideration before performing the seize operation is the administrator's group membership, as this table lists:

FSMO Role	Administrator must be a member of
Schema	Schema Admins
Domain Naming	Enterprise Admins
RID	Domain Admins
PDC Emulator
Infrastructure

To seize the FSMO roles by using Ntdsutil, follow these steps:


Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.

1. On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\WINDOWS>ntdsutil
ntdsutil:

1. Type roles, and then press ENTER.

ntdsutil: roles
fsmo maintenance:

Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER.

1. Type connections, and then press ENTER.

fsmo maintenance: connections
server connections:

1. Type connect to server , where is the name of the server you want to use, and then press ENTER.

server connections: connect to server server100
Binding to server100 ...
Connected to server100 using credentials of locally logged on user.
server connections:

1. At the server connections: prompt, type q, and then press ENTER again.

server connections: q
fsmo maintenance:

1. Type seize , where is the role you want to seize. For example, to seize the RID Master role, you would type seize rid master:

Options are:

Seize domain naming master
Seize infrastructure master
Seize PDC
Seize RID master
Seize schema master

1. You will receive a warning window asking if you want to perform the seize. Click on Yes.

fsmo maintenance: Seize infrastructure master
Attempting safe transfer of infrastructure FSMO before seizure.
ldap_modify_sW error 0x34(52 (Unavailable).
Ldap extended error message is 000020AF: SvcErr: DSID-03210300, problem 5002 (UNAVAILABLE)
, data 1722

Win32 error returned is 0x20af(The requested FSMO operation failed. The current FSMO holde
r could not be contacted.)
)
Depending on the error code this may indicate a connection,
ldap, or role transfer error.
Transfer of infrastructure FSMO failed, proceeding with seizure ...
Server "server100" knows about 5 roles
Schema - CN=NTDS Settings,CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net
Domain - CN=NTDS Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net
PDC - CN=NTDS Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net
RID - CN=NTDS Settings,CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net
Infrastructure - CN=NTDS Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net
fsmo maintenance:

Note: All five roles need to be in the forest. If the first domain controller is out of the forest then seize all roles. Determine which roles are to be on which remaining domain controllers so that all five roles are not on only one server.

1. Repeat steps 6 and 7 until you've seized all the required FSMO roles.
2. After you seize or transfer the roles, type q, and then press ENTER until you quit the Ntdsutil tool.

Note: Do not put the Infrastructure Master (IM) role on the same domain controller as the Global Catalog server. If the Infrastructure Master runs on a GC server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a GC server holds a partial replica of every object in the forest.

***************************************************************

It still did not work. I had to do the following:

Tick the checkbox for 'Global Catalog'. Only then it fully functions as a domain controller.

**************************************************

Converting a Win 2003 server to ADC:

Did not work in the straight forward way.

Had to give the following command in the DC:

c:> adprep /forestprep.

Only then could i make the new Win 2003 server into ADC.

Kaseya - Reset password

Question
How do I reset my Kaseya master admin password?

Answer
Both the username and password are case sensitive. Be sure to type in your username exactly as you entered it when you installed Kaseya originally. The default login policy deactivates an account for one hour after 5 bad login attempts. You can adjust this policy using the Login Policy function under the System tab.

If you have forgotten either the username or password you can set a new account as follows.
Note: For security reasons, you cannot perform the following procedure remotely. You must perform these steps locally on your Kaseya server.

1. Log in to the machine running the server component of the system.
2. Access the following web page: http://localhost/LocalAuth/setAccount.asp
3. Enter a new account name in the Master Administrator Name field.
4. Enter a password in the Enter Password field and confirm it by re-typing it in the Confirm Password field.
5. Press Create.

You can now log into the system as a master administrator.