HOW TO SWITCH DHCP SERVER

BELOW IS THE STEP BY STEP PROCESS TO SWICH DHCP SERVER FROM OLD TO NEW:

1. Log on to the source DHCP server by using an account that is a member of the local Administrators group.
2. Click Start, click Run, type cmd in the Open box, and then click OK.

3. Type netsh dhcp server export C:\dhcp.txt all , and then press ENTER.

4. Move the file to a network location
    If your are not enterprise admininistraor then contact your enterprise administrator 
    to complete below steps:
5. Authorize the new server
6. Change the IP-Address to another one and shutdown the Server.

Note: You must have local administrator permissions to export the data.

Import the DHCP database
1. Logon to the new Server and Change the IP-Address to the old DHCP Server Address
2. Copy the exported DHCP database file to the local hard disk of the Windows Server 2008-
     based computer.
3. Verify that the DHCP service is started on the Windows Server 2008-based computer.
4. Click Start, click Run, type cmd in the Open box, and then click OK.
5. At the command prompt, type netsh dhcp server import c:\dhcpdatabase.txt all , and then
    press ENTER, where c:\dhcpdatabase.txt is the full path and file name of the database file
    that you copied to the server.
(Check with your enterprise administrator is the new DHCP IP address same as old server if not tell him/her change that maually.)

Blackberry Enterprise Activation

Enterprise Activation




Device Software Version 5.x
The device must first be activated on your phone carrier network and registered on the BlackBerry Network.The device must have an active account on the BlackBerry Enterprise Server and have Enterprise Activation enabled for this process to be successful. Contact the BlackBerry Enterprise Server Administrator for more assistance.


1. From the Home screen, press the Menu button.
2. Select Options.
3. Select Advanced Options.
4. Select Enterprise Activation.
5. Enter the appropriate email address, password, and server address (if applicable) then press the Menu button.
           Activation password and server address must be obtained from the BlackBerry Enterprise Server     
           Administrator.
6. Select Activate.
           Activation times vary and may be thirty minutes or more.
7. Select OK.


Device Software Version 6.x

1. From the Home screen All tray, select Setup.
    To expand the tray, press the Menu button then select Maximize Tray.
2. Select Email Accounts.
    If presented, review the End User Agreement then select I Accept to continue.
3. Select Enterprise Account.
    If not presented, Perform a Register Now then repeat steps 1 and 2.
4. From the Account Activation section, enter the following information then select Activate:
   Activation times vary and may be thirty minutes or more.
   o Email
   o Activation Password
5. Select OK.

OUTLOOK 2010 SIGNATURE

In Office 2010 the location of some of the previously inherited options are different. If you are familiar with Outlook 2007 and have recently migrated to the Office 2010 then you might be wondering about from where you can add signatures to your emails. Here are the steps to add signatures in Outlook 2010.

• First of all click the Office button, and the go to Outlook > options. The Outlook Options dialogue box will be displayed.
• Now click the Mail option located in the left side menu, and locate the create and modify signatures for message option in the right side main window.
• Now click the Signatures button located in front of the create and modify signatures for message option. The Signatures and Stationary dialogue box will be displayed, now in order to add new signatures, click the New button.
• Here add your signature’s text under the Edit signature text area and click the OK button.
• Now your personal signature will appear at the end of every email you send. Enjoy!

Software Testing Course

If you want to learn Software Testing please contact at sarwarrashed@hotmail.com

This is a web based training session. You will have the opportunity to listen and interact with instructor and course attendees live. You can ask your specific questions and receiving real-time answers

Some Usefull Commands

You can open some program without using mouse. Please see below:

TO OPEN MS PROGRAMS:
Press Windows key + R together. In the open window type commands and press enter
Microsoft Word : winword

Microsoft Excel : excel

Microsoft Access : msaccess

Microsoft PowerPoint : msppt

TO OPEN WINDOWS PROGRAMS:
Press Windows key + R together. In the open window type commands and press enter

Notepad : notepad
Calculator : calc
Windows Explorer : explorer.exe
Internet Explorer : iexplorer.exe
Command prompt : cmd
MS Paint : mspaint
Windows Service : services.msc
Remote desktop : mstsc (Then type the IP address or PC name)


IN COMMAND PROMPT TYPE BELOW COMMANDS TO VIEW SOME SETTINGS:

To see logon server: type SET
To change logon server: type SET LOGONSERVER=\\YOUR SERVER NAME
To see IP configuration: type IPCONFIG /ALL
To trace a remote host: type TRACERT IP ADDRESS OR PC/SERVER NAME

HOW TO INSTALL WINDOWS XP / SERVER 2003 WITH SATA DRIVERS

Recent days hardware manufacturers come with new idea that is SATA hard drive, SATA CD ROM drive for speeding up data transfer. Some time it’s hard to install windows operating system when your operating installation CD is old version but the hardware is new. Problem because of SATA driver we need does not come embedded in the Windows XP or Server installation package. To solve this issue we can follow below method.
Ingredients are involved in this operation:
1. The original Windows XP or Server Installation CD
2. A freeware application named
NLite
3. A blank CD
4. SATA controller drivers provided by the manufacturer.
STAT drivers could be found in floppy inside the motherboard package or you can download from manufacturer web site. After download the drivers unzip them (in case they come archived) in a desired location. Then download and install the Nlite (download from above linked web site) application. When you start the Nlite application, you will be asked to provide the location for the Windows installation package. Insert the genuine Windows Installation CD into the CD drive and, inside the application, select the CD drive letter.

To insert the SATA drivers within the installation package, you need to have it saved on the HDD. Hence, when the warning window appears click OK and select the destination folder for the files to be saved. Make sure that the destination partition / HDD has enough space to store the contents of the installation CD.
I tested a Windows Server 2003 standard edition and it seems that it required about 569 MB. Immediately after you have chosen the destination folder, the application will start copying the Windows installation files. When finished, it will display some version information regarding the newly copied Windows Installation Package.
Now, click next twice until you get to a screen where you get options sorted in 4 categories: Integrate, Remove, Setup, Create (left side of the window). We are interested in the integration procedure, therefore select the Drivers button and click next. From the next menu window, click Insert and select multiple drive folder option from the drop down menu. This option permits you to browse to the location where the downloaded drivers are found.
Select the containing directory and click next. You will get a list with the available drivers (in case there are more than one) or simply one driver. Select it (them) and click next. Now the application will ask for the permission to start the integration procedure. Choose Yes and wait for the drivers to be inserted into the installation package.
With problematic driver being included in the installation package you can install Windows XP or Server on your SATA HDD...but...the installation package is on the HDD. You need a bootable CD in order to start an installation. Don't worry, once the installation package has been adorned with additional user selected drivers it can be transformed into a bootable disk image and later burned on a CD. To encapsulate the installation into a ISO image use the same Nlite application.
Open it, make sure the HDD installation folder is selected and click next. Select "Last session" preset and click next again. Now from the options menu choose Bootable ISO and click next. In the following window, make sure that the mode is set to "Create Image" and click Make ISO. A destination folder is required where the resulting ISO image will be saved. Once the image saving process finished you have the freedom to burn it on a blank CD with whatever you favorite CD burner software may be. Go to www.download.com and you will find lots of freeware to burn your ISO image.
The new CD will be the twin copy of the Windows Installation CD but with one difference, it includes the SATA driver.

Symantec 10.1 Issues

Moving Symantec AntiVirus Corporate Edition 10.x clients from one parent server to another

Situation: You have installed Symantec AntiVirus Corporate Edition 10.x (Symantec AV) clients as a managed client of a Symantec AV 10.x server, and now you want to move the client or clients to a different parent server. Solution: You can do that by first method but that will give you and your co-worker a big headache, but you can complete your mission without headache and less effort.

1. “Manually move clients to different parent server”
2. “Moving one or more clients to a different parent server"
3. "Moving all clients to a different parent server,"

Manually move clients to different parent server

Uninstall Symantec Client security form your client PC. To uninstall follow below method

• Open Control panel
• Click Add/Remove Programs
• Select Symantec Client Security and click Remove (At the end of uninstall process it will ask for restart PC, but don’t restart now.)
• Select Symantec Live Update and click remove.
• Now restart client PC and login as user or admin.
• Deploy Symantec Client security form the Server.
• Open Symantec System center console
• Select your server group then select your server.
• Click Tools > Client Remote Install (It will open up the Installation wizard)
• Click Next
• In the location select default and click Next
• In the computer selection center from the left panel select your computer (Double click Microsoft windows network, double click your domain)
• From the right panel select the server name then click Add (You will the select client PC shows under select sever)
• Click finish and it will deploy Symantec client security on respective client PC. After finishing deployment click Done and close Symantec System center console

The above process you can use for first time deployment of client. In that you don’t need to uninstall anything just follow the deployment process.

Moving one or more clients to a different parent server

If you want to move a few clients to a different server, then copy the Grc.dat file from the new parent server to all the clients that you want to be managed by the new parent server. This can be done through many distribution methods, the most common being login scripts.Where to find the Grc.dat file on the parent server

• If the parent server is Windows NT or 2000, 2003 then copy the Grc.dat file from the VPHOME shared folder on the parent server. By default, the VPHOME shared folder is pointing to C:\Program Files\SAV on the parent server.
• If the parent server is NetWare, then copy the Grc.dat file from the SYS:SAV folder. Note: If you want to move the clients to a different parent server and also add them to a specific client group, use the Grc.dat file from the directory \SAV\Groups\, where represents the name of the client group. Where to put the Grc.dat file on the clientCopy the Grc.dat file to the appropriate folder for your operating system.

** Windows 98: The default folder location is C:\Program Files\Symantec_Client_Security\Symantec AntiVirus\.

**Windows NT: The default folder location is C:\WinNT\Profiles\All Users\Application Data\Symantec\NortonAntiVirus Corporate Edition\7.5\.

**Windows 2000/XP: The default folder location is C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

Note: On Windows 2000/XP, the directory "Application Data" (C:\Documents and Settings\All Users\Application Data) is hidden.

If you have clients using Norton AntiVirus Corporate Edition 7.5 or 7.6, the appropriate folders are as follows:

**Windows NT: The default folder location is C:\WinNT\Profiles\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

**Windows 2000/XP: The default folder location is C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

Note: On Windows 2000/XP, the directory "Application Data" (C:\Documents and Settings\All Users\Application Data) is hidden.

**Windows 95/98/Me: The default location for this version is C:\Program Files\Norton AntiVirus\.

After a few minutes, the Symantec AV client will find the Grc.dat file in this folder. Symantec AV will make the appropriate changes to the registry and will delete the Grc.dat file.

Note: If you do not uninstall the Symantec AV Server software from the original parent server, then client computers may show up in the Symantec System Center (SSC) under both servers for 30 days. The old Symantec AV server retains the client's information in its cache for 30 days after it stops receiving "keepalive packets" from that client. To avoid or solve this problem, see the section “How to remove clients from the Symantec System Center”.

Moving all clients to a different parent server

If you want to move all clients to a different parent server, then changing a specific registry key on the original parent server will automatically direct clients to a new parent server. If the current parent server is no longer functioning, then use Method 2.

WARNING: I strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure that you modify only the keys specified.

1. Navigate to the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\ClientConfig\
2. Change the "Parent" name to the computer name of the new parent server.
3. Change "RemoteHomeDirectory" name to the new parent server.
4. If you are migrating clients across server groups, navigate to the following registry subkeys:HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\DomainDataand change "DomainName" to the new server group name in each.
5. Close the Registry Editor.
6. Open Symantec System Center.
7. Right-click the original parent server, point to All Tasks, point to Symantec AntiVirus, and then click Client Realtime Protection Options. Note: If the clients are in client groups, right-click the client group instead of the parent server. You will need to do this for each client group.
8. Click Reset All. This will generate a new copy of the Grc.dat file that refers clients to the new parent server.When the clients check in to the original parent server, they will receive the configuration change and begin communicating with the new parent server. If you stop and then restart the Symantec AV Server service or reboot the original parent server, then the Grc.dat file will again refer clients to the original parent server. Any clients that did not receive the configuration change will still be managed by the original parent server.

Note: If you do not uninstall the Symantec AV Server software from the original parent server, then client computers may show up in the Symantec System Center (SSC) under both servers for 30 days. The old Symantec AV server retains the client's information in its cache for 30 days after it stops receiving "keepalive packets" from that client. To avoid or solve this problem, see the section How to remove clients from the Old Symantec System Center to New Symantec System Center

How to move clients from the old Symantec System Center to New Symantec System Center

If you follow the last two methods may be you will not see the clients computers in SSC. Follow below the steps to see your clients PC under your new parent server SSC. Copy the xxx.xservergroupca.cer from New Parent server’s C:\Program Files\Sav\pki\roots to Client PC’s C:\Program Files\Symantec Client Security\Symantec AntiVirus\pki\roots. If you install Symantec System Center Console in D or E drive of parent server then copy the xxx.xservergroupca.cer file from D:\Program Files\Sav\pki\roots or E:\Program Files\Sav\pki\roots Wait for five to ten minute and you will see your client PC in New Parent server. If not then force the client PC to check with parent server by following steps On the client machine open regedit and goto HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\ProductControl

Change the value from 0 to 1 of ReloadRootCertsNow key Change the value from 0 to 1of ReStartPongEngineNow

If these fields do not exist create a DWORD value and name them accordingly