how to restore corrupted system files

Apart from booting system in command prompt from boot cd/floppy, you have following two option to restore corrupted system file.

1. use sfc utility.
Go to command prompt in windows and type sfc /scannow . This will check all windows system files and find out which one is corrupted. At the end of the process it will ask for windows CD. Put the CD in ROM and it will restore file for you.

2. restore file thru msconfig.
Go to run and type msconfig. In msconfig windows click on expand file. From here you can restore the file.

Modem in Bridge mode - PPPOE cofiguration for router

Important Points

1. Even if your ISP has assigned you static ip address. DO NOT configure this IP address on dialer interface. Use ip address negotiate command. Once router authenticated, it will automatically get that static ip address.
2. When you configure leave in a bridge mode, leave DHCP service on the modem ON.
3. Ask your service provider for authentication method and configured same on the router. In this example I have used PAP authentication.

Troubleshooting steps.
1. Use debug PPPOE events command on routers to see the event.
2. If connection is not working, then directly connect the modem to the PC (while leaving modem is a bridge mode and DHCP service on the modem on) and setup PPPOE connection on the PC and test it by using your connection credentials.


Building configuration...

Current configuration : 2926 bytes
!
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
dot11 syslog
ip cef
!
!
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
!
username myname privilege 15 secret 5 $1$4CDH$.3D11txHCBPBAidX/CnW5.
username yourname privilege 15 secret 5 $1$NcnE$mjiu4M0YaY0uksZ5cLrKJ0
!
!
crypto isakmp policy 1
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp key XYZ address X.X.X.X
!
!
crypto ipsec transform-set aes-sha esp-3des esp-sha-hmac
!
crypto map VPNtoBlacktown 10 ipsec-isakmp
set peer X.X.X.X
set transform-set aes-sha
match address VPN-Traffic
!
archive
log config
hidekeys
!
!
!
!
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface FastEthernet4
description connected to WAN
no ip address
ip virtual-reassembly
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
!
interface Vlan1
description connected to LAN
ip address 192.168.250.30 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!
interface Dialer0
ip address negotiate
ip mtu 1492
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
ppp authentication pap callin
ppp pap sent-username XYZ password 0 ABC
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
!
ip http server
no ip http secure-server
ip nat inside source list NAT-Traffic interface Dialer0 overload
!
ip access-list extended NAT-Traffic
deny ip 192.168.250.0 0.0.0.255 192.168.1.0 0.0.0.255
deny ip 192.168.26.0 0.0.0.255 192.168.1.0 0.0.0.255
permit ip 192.168.250.0 0.0.0.255 any
permit ip 192.168.26.0 0.0.0.255 any
ip access-list extended VPN-Traffic
permit ip 192.168.26.0 0.0.0.255 192.168.1.0 0.0.0.255
permit ip 192.168.250.0 0.0.0.255 192.168.1.0 0.0.0.255
!
!
!
control-plane
!
banner motd ^C
This is the branch router for XYZ.
Access to this system is restricted solely to employees
of XYZ Personnel and authorised service personnel.

************************************************************************
* WARNING: It is a criminal offence to: *
* i. Obtain access to data without authority *
* (Penalty 2 years imprisonment) *
* ii Damage, delete, alter or insert data without authority *
* (Penalty 10 years imprisonment) *
************************************************************************^C
!
line con 0
login local
no modem enable
line aux 0
line vty 0 4
login local
transport input all
!
scheduler max-task-time 5000
end

Security logs full - cannot logon

The security log on this system is full. Only administrators can log on to fix the problem.

An attempt to log on remotely is greeted with:

The security log on this system is full.

Only members of the Administrators group can log on when the Security event log cannot be written.

To resolve this issue for the user:

1. Log on to the computer as a member of the Administrators group.

2. Start / Run / eventvwr.msc / OK.

3. Right-click Security and press Properties.

4. Either clear the event log, make it bigger, or check Overwrite events as needed.

5. Press OK.

6. Close the Event Viewer.

POP3 service stuck in starting state

When POP3 service stuck in starting state, check task manager and look for inetinfo.exe.

End this process manually and POP3 service should be fine now.

Note: inetinfo.exe is used primarily for debugging Microsoft Windows Server Internet Information Services. So start this process once POP service is in started state.

How to configure notification and reporting in Data Protector

1. Create an account in active directory called dpadmin. This account should be mail enable and IMAP enable.
2. Start data protector CRS service using this account. Stop and start CRS service.
3. Login to the server using dpadmin account and setup outlook express for dpadmin account. Check you can send and receive emails using outlook express now.
4. If sending and receiving of emails is successful then add dpadmin username in admin list in data protector console.
5. Open following file in notepad.
\config\server\options\global
Change following things.
SMTPSERVER=out going server
smtpsenderaddress= dpadmin@domainname i.e email address
6. Stop and start DP services.
7. Open outlook express ant go to tools -> accounts and delete all accounts other then dpadmin mail account.
8. In outlook express go to tools -> options -> security and uncheck the option warn me when other application try to send email as me.
9. Take backup of \omnirc.tmpl and rename this file to omnirc (without any extension). Add following line in the file
OB2_MAPIPROFILE=dpadmin
10. Search for mapi32.dll and check the path of the file. It would be C:\windows\system32. Check path variable and if this path is not there then add this path C:\windows\system32.
11. Stop and start DP services.
12. Testing – open command prompt and use following command
Omnirpt -report cell-info –email ravi.parmar@indicium.com.au –exec
13. If it works then open DP GUI and configure notification and reports.

Blackberry services order

When you restart Blackberry services, restart them in following order :
1 . BB Router
2 . BB Dispatcher
3 . BB Controller
4 . whatever is left, you can start them in any order.

Blackberry - Activation Problem

When you try to activate blackberry and it stucks at saying

encryption verified...
................
..............
"waiting for the services"

Then it can be services issue. ensure that following services are started on BES.

Blackberry Policy Service
Blackberry Synchronization Service

To activate new BB, this services must be started.

Setting the location of the BES server log files.

1. Open BlackBerry Server Configuration.

2. Click the Logging tab.

3. Press the Browse button [...] and choose the desired location of the log files.

4. Apply settings and press OK button close window.

Outlook - Meeting appointment Problem

When you send meeting appointment to someone and you receive following error message :
The following recipient(s) could not be reached:
/O=XYZ/OU=FIRST ADMINISTRATIVE
GROUP/CN=RECIPIENTS/CN=rparmar on 2008/02/20 17:54
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.The MTS-ID of the original
message is:c=us;a= ;p=xyz;l=XYZPERSER1-080220085403Z-1384



Then it s delegation issue. Check outlook of the meeting appointment recepient.
Go to Tool -> Options -> delegates and remove delegates to users(in this case rparmar) who no longer exists in active directory.

This will reslove the issue.

how to restore exchange database using RSG and Data Protector

1.Create Recovery Storage Group on the server.
2.Add database to RSG.
Make sure you select different location for database file and streaming file(different location from Original files) and ensure that “This database can be overwritten by a restore” checkbox is checked.
3.Now on data protector select database to be restored. Select the correct version and make sure that tapes are in drive.
NOTE : if tape is expired and you get error in restoration . Do “import Catalog ” for that tape.
On options tab, specify the directory for temporary files
4.Once database is restored then use eseutil to check whether database is in clean shutdown state or Dirty shutdown state. Use following command to check it

Eseutil /mh "Full path of restored .edb file"

5.if the database is in “Dirty shutdown ” state use following command to fix the database file.

Eseutil /p /i "Full path of restored .edb file"

It takes quite long time to fix database file and it depends on the size of database.

6.Once the above process finish , use command in step 5 to make sure that database is in clean shutdown state.
7.once database is in clean shutdown state then Go back to Exchange manager and do “Mount store” on RSG.
8.Once database is mounted, use Exmerge to restore mailbox to PST file.

Steps to restore Exchagne 2003

Steps to restore exchange server 2003
1. Replace any damaged hardware. If possible, ensure that all replacement hardware in the server you are rebuilding is identical to the hardware that existed in the server that experienced the disaster.
2. Install windows 2003 on the server that you are rebuilding.
3. Restore the windows backup set that was performed on the damaged server to the
server you are rebuilding. Restoring the windows backup set restores the windows 2003
system files, including the registry database and internet information services metabase files. This process also provides the server that you are rebuilding with its original NetBIOS name and returns it to the correct domain. If you do not perform this step, you cannot properly run setup in disaster recovery mode.
4. Install any windows 2003 service packs and software updates that were running on the damaged server to the server you are rebuilding.
5. Install any application (other than exchange server 2003) that run on the server.
6. Restore any additional data backups that were performed on the damaged server.
7. Run exchange server 2003 setup in disaster recovery mode. This process installs
exchange applications and any necessary exchange files to the server you are rebuilding. This process also uses the configuration information that is stored on the exchange server object in Active directory to reclaim the configuration of the original server. The configuration information that is reclaimed includes the exchange storage group names, mailbox store names, public folder store names, and virtual server configuration settings. When you run exchange in disaster recovery mode, ensure that all the components that existed on the damaged server are selected.
8. If not already selected, select disaster recovery for each component that was installed on the damaged server.
9. Install Exchange server 2003 to the same drive and directory that it was installed to on the damaged server. At a minimum, you should ensure that all the drive letters on which databases and log files were kept are available.
10. Install any exchange server 2003 hotfixes that were running on the damaged server.
11. Install in disaster recovery mode any exchange server 2003 service packs that were running previously on the damaged server to the server. Installing exchange server 2003 service packs in disaster recovery mode prevents the exchange databases from being mounted at the end of the service pack installation process, which enables you to proceed to restoring the exchange databases from backup.
12. After exchange database restore, check the state of the database by using eseutil. If they are in dirty shutdown state, use eseutil to covert them to clean shutdown state. Once exchange databases are in clean shutdown, you can mount them.
13. Restore exchange database files and log files to the correct locations from the backup.
14. If you do not have the latest log files then you will lose changes that were made to exchange databases up to the time the disaster occurred.