Aug 30, 2009

Linux Pocket Reference For System Administrators
Download:Book
Video Codec for wintendo:
System Trouble Shooting (Good for RHCE preparations ! ):
Linux Advance Administration CBTs
Installation:
Basics:
Miscellaneous Servers:
 
Qmail :
 


Samba:



Squid:


SquidGuard:
Joomla CBTs

Aug 29, 2009

Introduction to Windows Server 2008

Windows 7 - First Look

Hiren's BootCD From USB Flash Drive (USB Pen Drive)

 Step 1
Connect USB Pen Drive (256Mb or more)

Step 2
Download and Run USB Disk Storage Format (34KB)



Step 3
Download and Run grubinst_gui (147KB)



Step 4

Copy grldr and menu.lst to the usb drive



 Step 5

Insert the BootCD (9.7) in the CD Drive and Copy everything from CD to USB Flash Drive

Step 6

Test Your USB Drive (read bottom of the page for troubleshoot)


Make sure you set your computer to boot from USB Flash Drive


To Enter the BIOS press the "Del" button on your keyboard. Alternatives are "F1", "F2", "Insert", and "F10". Some PC's BIOS might even require a different key to be pressed. Commonly a PC will show a message like "Press [Del] to enter Setup" to indicate that you need to press the "Del" key. Some AMI BIOS require you to enable the option "USB Keyboard Legacy support"!


For AMI BIOS:


• Go to "Feature Setup". "Enable" these options: "USB Function Support",


"USB Function For DOS" and "ThumbDrive for DOS". Go to "Advanced Setup".


Set the "1st Boot Device" to "USB RMD-FDD".


Reboot the PC and it now should boot from the Usb Stick.
• Go to "USB Mass Storage Device Configuration". Select "Emulation Type"
and set it to "Harddisk". Go to the "Boot Menu" and set the "1st boot device" to "USB-Stick". Exit the BIOS, saving the changes.
you can try "Emulation Type" to "Floppy" or "Forced FDD".


For PHOENIX/AWARD BIOS:

• Go to "Advanced BIOS Features". Go to the "1st Boot device" and set it to "USB-ZIP"
How To Disable "Autorun.Inf "

Tags: tips
Recently there are many case reported that 'autorun' virus spread through so many computer due to using flash memory or pendrive,so we need a preventive action to stop this virus spread to our computer.



As we insert a pendrive to computer,window will scan and check is there have 'autorun.inf' file and then write into 'mountpoint2' registry,'mountpoint2' will amend the act to open a disk or pop up menu.Although you already set up ' disable auto play' ,use right click or use 'explore' to open disk,the result still will run 'virus .exe'.



Therefore,we need to banned the 'mountpoint2' registry area,the method as below,



1.START ->RUN ->Key in 'regedit' to open registry.
2. HKEY_CURRENT_USER\ Software\Microsoft\ Windows\CurrentVersion \Explorer\MountPoints2,
3.Right click 'mountpoints2' and select 'permission'
4.Then click 'Advance',uncheck 'inherit from parent the permission entires that apply to child objects.Include these with entires explicity defined here'.
5.Click 'remove'.'Yes' and 'ok'.




Now,even you insert a pendrive with virus and your computer couldn't affected.
How to disable USB sticks and limit access to USB storage devices on Windows systems
USB storage - a possible security risk?


Decent IT administrators secure their networks behind firewalls. They install mail filters on their SMTP servers and deploy anti-virus software on all client workstations. But securing the network is not sufficient -- what happens if the users bring their own USB memory sticks and connect them to the computers at their office? A 1 Gb USB stick can sometimes hold an entire company's vital data. Within minutes or even seconds an employee has all the files they need in order to start up their own business and take all the customers with them. Alternatively, what happens if a careless user accidentally compromises the network with an infected USB stick?
What does Microsoft have to say about it?
If you, the administrator, want to establish a minimum level of security, it is absolutely necessary to control which users can connect USB memory sticks to a computer. Unfortunately, a default Windows XP or Windows 2000 installation comes with no limitations on who is able to install and use USB storage media. Microsoft knowledge base article 823732 contains instructions on how to disable USB storage access for a certain group of users; however, the article only distinguishes between whether or not a USB storage device has been installed on a particular computer. Furthermore, the instructions are limited to a stand-alone computer. According to the general rule of thumb "If it's tedious, there is a better way", I try to avoid techniques that force me to repeat certain tasks for each computer that I manage. That's what group policy objects (GPO) are for.
Suggestions?
Mark Heitbrink describes how to disable USB storage devices entirely on all or some computers in the network. He employs an ADM template in a group policy object that disables the USB storage driver (USBSTOR). The ADM template simply sets the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor\Start to 4 (Disable). But his technique has a serious drawback. It only works if the USB storage driver is already installed. If it has not yet been installed, Windows' plug & play subsystem automatically resets the Start value to 3 (Manual) when it installs USBSTOR after a USB storage device is plugged in for the first time. In that case, USBSTOR remains enabled until the GPO is re-applied, usually at the next reboot. If the storage device is plugged in during that reboot, it will still be available because the USBSTOR driver is started before any GPOs are processed.
The Howto!
If we combine Mark Heitbrink's approach with the one outlined in knowledge base article 823732, we get a more reliable solution. Firstly, we need to prevent USBSTOR from being installed unless the currently logged on user is allowed to use USB storage. We do that by restricting access to USBSTOR.INF and USBSTORE.PNF in a GPO such that PNP can't automatically install the driver. This is possible because when PNP installs a driver, the installation is performed using the priviledges of the currently logged on user. Secondly, we need to make sure that USBSTOR is not started when a USB storage device is plugged in. For that we use Mark's ADM template. The only minor drawback of my solution is that users with access to USB storage need to manually start USBSTOR before connecting USB storage devices.
1.In Active Directory Users and Computers, open an existing GPO or create a new one and open it. Use the security settings of that GPO to specify which computers it affects.

2.In that GPO, go to Computer Configuration – Windows Settings – Security Settings – File System and create a new entry (right-click File System and select Add File). Specify the location of USBSTOR.INF (usually SystemRoot%\Inf\USBSTOR.INF)

3.Change the security settings of the new entry. The security settings that you specify here will be enforced on the USBSTOR.INF of every computer to which the GPO is applied. This process is not additive, which means that the previous security settings of USBSTOR.INF will be overwritten by the ones given in the GPO. It is therefore recommended to grant full control to SYSTEM and local administrators. But unlike in the default security settings of USBSTOR.INF, you should not grant any priviledges to Everybody. You do not need to explicitly deny access – just omit an entry for Everybody. Optionally, you can grant read access to a certain group. Members of this group will be able to use USB storage.
4.Repeat the above two steps for USBSTOR.PNF.
5.Download USBSTOR.ADM.
6.Back in the GPO, right-click Administrative Templates under Computer Configuration and select Add/Remove Templates. Click Add and browse to the location of USBSTOR.ADM. Close the dialog.

7.You should now have an additional entry called Services and Drivers in Administrative Templates. Click on it. If it is empty, select View from the menu and uncheck Show Policies Only. Click back on Services and Drivers in Administrative Templates. It should now show the USB Storage policy. Double click it, select Enabled and pick Disabled from the Startup Type drop down. Again, the policy must be enabled wheras Startup Type must be Disabled.

8.Close the dialog as well as the GPO and boot/reboot one of your workstations. Make sure no USB strorage device is connected to that computer. Log on with administrative privileges and check the permissions of USBSTOR.INF and USBSTOR.PNF. Check the value of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor\Start. It should be 4. It is also ok if the UsbStor key doesn't exist at all.

9.On the same workstation, log off and back on as a user that should not have access to USB storage. Connect a USB memory stick or a similar device. Nothing should happen. Remove the memory stick.

10.Log on as a user that should have access to USB storage and execute net start usbstor in a command shell or at Start – Run before connecting the memory stick. The memory stick should initialized and mapped to a drive letter. If USBSTOR fails to start, it's probably because this is the first time a memory stick is plugged into the workstation in which case USBSTOR is not yet installed. Nevertheless, the memory stick should be initialized and mapped correctly but you need to reboot in order to reapply the administrative template such that USBSTOR is disabled again. Alternatively, you can disable it manually by downloading and double clicking USBSTOR.REG as well as executing net stop usbstor.

11.Instruct the users with access to USB storage that they need to execute net start usbstor before they can connect a USB storage device.
How to Repair this SVCHOST.EXE error

After some investigating into the 0X745f2780 SVCHOST error, it became apparent the problem is a corrupted Windows Update in Windows XP. Follow the steps below to fix this error.



Verify Windows Update Service Settings
Click on Start, Run and type the following command in the open box and click OK
services.msc


Find the Automatic Updates service and double-click on it.

Click on the Log On Tab and make sure the "Local System Account" is selected as the logon account and the box for "allow service to interact with desktop" is UNCHECKED.

Under the Hardware Profile section in the Log On Tab, make sure the service is enabled.


On the General Tab, the Startup Type should be Automatic, if not, drop the box down and select Automatic.


Under "Service Status" on the General tab, the service should be Started, click the Start button enable it.


Repeat the steps above for the service "Background Intelligent Transfer Service (BITS)"


Re-Register Windows Update DLLs


Click on Start, Run, and type CMD and click ok
In the black command window type the following command and press Enter


REGSVR32 WUAPI.DLL
Wait until you receive the "DllRegisterServer in WUAPI.DLL succeeded" message and click OK


Repeat the last two steps above for each of the following commands:

REGSVR32 WUAUENG.DLL
REGSVR32 WUAUENG1.DLL
REGSVR32 ATL.DLL
REGSVR32 WUCLTUI.DLL
REGSVR32 WUPS.DLL
REGSVR32 WUPS2.DLL
REGSVR32 WUWEB.DLL


Remove Corrupted Windows Update Files
At the command prompt, type the following command and press Enter


net stop WuAuServ
Still at the command prompt,
type cd %windir% and press Enter


In the opened folder, type the following command and press Enter to rename the SoftwareDistribution Folder

ren SoftwareDistribution SD_OLD
Restart the Windows Update Service by typing the following at the command prompt


net start WuAuServ


type Exit and Press Enter to close the command prompt


Reboot Windows


click on Start, Shut Down, and Restart to reboot Windows XP
Although this method may not solve all of the issues with a SVCHOST.EXE Application error, I have found it fixed the problem with the 0x745f2780 reference error.


Other Issues with SVCHOST.EXE

I've encountered other issues with SVCHOST taking up 100% of the CPU Cycles. These issues are usually experienced with Windows Update in some form or another. To fix this frustrating problem, following these steps:


1) Download and install Update for Windows XP (KB927891)
2) Download and install an update for Windows Update Agent WSUS 3.0
3) Restart your computer and your computer should run better with slowing to a crawl because of SVCHOST.EXE

Svchost.exe

What is svchost.exe And Why Is It Running?

You are no doubt reading this article because you are wondering why on earth there are nearly a dozen processes running with the name svchost.exe. You can’t kill them, and you don’t remember starting them… so what are they?

So What Is It?

According to Microsoft: “svchost.exe is a generic host process name for services that run from dynamic-link libraries”. Could we have that in english please?

Some time ago, Microsoft started moving all of the functionality from internal Windows services into .dll files instead of .exe files. From a programming perspective this makes more sense for reusability… but the problem is that you can’t launch a .dll file directly from Windows, it has to be loaded up from a running executable (.exe). Thus the svchost.exe process was born.

Why Are There So Many svchost.exes Running?

If you’ve ever taken a look at the Services section in control panel you might notice that there are a Lot of services required by Windows. If every single service ran under a single svchost.exe instance, a failure in one might bring down all of Windows… so they are separated out.

Those services are organized into logical groups, and then a single svchost.exe instance is created for each group. For instance, one svchost.exe instance runs the 3 services related to the firewall. Another svchost.exe instance might run all the services related to the user interface, and so on.
So What Can I Do About It?



You can trim down unneeded services by disabling or stopping the services that don’t absolutely need to be running. Additionally, if you are noticing very heavy CPU usage on a single svchost.exe instance you can restart the services running under that instance.

The biggest problem is identifying what services are being run on a particular svchost.exe instance… we’ll cover that below.
If you are curious what we’re talking about, just open up Task Manager and check the “Show processes from all users” box:

Checking From the Command Line (Vista or XP Pro)

If you want to see what services are being hosted by a particular svchost.exe instance, you can use the tasklist command from the command prompt in order to see the list of services.

Tasklist /SVC

The problem with using the command line method is that you don’t necessarily know what these cryptic names refer to.

Checking in Task Manager in Vista



You can right-click on a particular svchost.exe process, and then choose the “Go to Service” option.

This will flip over to the Services tab, where the services running under that svchost.exe process will be selected:


The great thing about doing it this way is that you can see the real name under the Description column, so you can choose to disable the service if you don’t want it running.

Using Process Explorer in Vista or XP

You can use the excellent Process Explorer utility from Microsoft/Sysinternals to see what services are running as a part of a svchost.exe process.

Hovering your mouse over one of the processes will show you a popup list of all the services:


Or you can double-click on a svchost.exe instance and select the Services tab, where you can choose to stop one of the services if you choose.


Disabling Services

Open up Services from the administrative tools section of Control Panel, or type services.msc into the start menu search or run box.
Find the service in the list that you’d like to disable, and either double-click on it or right-click and choose Properties.


Change the Startup Type to Disabled, and then click the Stop button to immediately stop it.

You could also use the command prompt to disable the service if you choose. In this command “trkwks” is the Service name from the above dialog, but if you go back to the tasklist command at the beginning of this article you’ll notice you can find it there as well.

sc config trkwks start= disabled



Hopefully this helps somebody!