December 2, 2011

Transfer Server Roles

netdom query fsmo

http://thaivmadmin.com/index.php/Windows-Server-Article/%E0%B8%A7%E0%B8%B4%E0%B8%98%E0%B8%B5-Promote-Domain-Controller-%E0%B8%9A%E0%B8%99-Windows-Sever-2003-R2.html

September 28, 2011

OUTLOOK - One time auto reply

REF: http://support.microsoft.com/kb/311107

The Rules Wizard rule to "reply using a specific template" is designed to send the reply only one time to each sender during a session. This prevents Outlook from sending repetitive replies to a sender from whom you receive multiple messages.

During a session, Outlook remembers the list of users to whom it has responded. When you restart Outlook, this list is deleted and the rule is reset to start again for each sender.

NOTE: Outlook must be running for the Rules Wizard to automatically reply. Additionally, Outlook 2007 must be running and configured to check periodically for new messages.

For additional information about how to emulate the Out of Office Assistant in Outlook Express, click the following article number to view the article in the Microsoft Knowledge Base:

September 23, 2011

The User Profile Service failed the logon.

http://support.microsoft.com/kb/947215

Remove s.. bak..
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList



Refcount=0
State=0

September 22, 2011

Firefox

about:config
Filter this key
dom.ipc.plugins

August 24, 2011

MSG to VCF ( Vcard) without 3rd software


In the OUTLOOK, go to contact
select any contacts you want to convert.
Click Forward contact as screen shown.
Then, copy .VCF from the draft email to
any folder you want.

July 23, 2011

Some points to improve the shutdown times

Start Registry Editor and navigate to the following key:

[HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

Set ClearPageFileAtShutdown value to 0

Or, using Group Policy Editor [for Windows XP Professional]

Click Start, Run and type Secpol.msc
Click Local Policies | Security Options
In the right-pane, set Shutdown: Clear virtual memory pagefile to Disabled

July 12, 2011

How to create acronis bootable on flash drive

1. format flash drive follow the screen.




2. copy menu.lstand grldr to flash drive




3. create folder and copy acronis.iso


=========menu.lst code=========
title Acronis True Image Home 2009 (9,615)
map (hd0,0)/acronis/AcronisMedia.iso (hd32)
map --hook
chainloader (hd32)
boot
=========



For more details refer to http://www.themudcrab.com/acronis_grub4dos.php

July 8, 2011

Exchange version

Version Number Service Pack Release Date
4.0.837.10 Microsoft Exchange Server 4.0 RTM April 1996
4.0.838.15 Microsoft Exchange Server 4.0 SP1 May 1996
4.0.993.40 Microsoft Exchange Server 4.0 SP2 (4.0a) August 1996
4.0.994.64 Microsoft Exchange Server 4.0 SP3 November 1996
4.0.995.54 Microsoft Exchange Server 4.0 SP4 April 1997
4.0.996.00 Microsoft Exchange Server 4.0 SP5 May 1998

5.0.1457.10 Microsoft Exchange Server 5.0 RTM March 1997
5.0.1458.50 Microsoft Exchange Server 5.0 SP1 June 1997
5.0.1460.13 Microsoft Exchange Server 5.0 SP2 February 1998

5.5.1960 Microsoft Exchange Server 5.5 RTM February 1998
5.5.2232 Microsoft Exchange Server 5.5 SP1 July 1998
5.5.2448 Microsoft Exchange Server 5.5 SP2 December 1998
5.5.2650 Microsoft Exchange Server 5.5 SP3 September 1999
5.5.2653 Microsoft Exchange Server 5.5 SP4 November 7, 2000

6.0.4417 Microsoft Exchange Server 2000 RTM October 2000
6.0.4712 Microsoft Exchange Server 2000 SP1 July 2001
6.0.5762 Microsoft Exchange Server 2000 SP2 December 2001
6.0.6249 Microsoft Exchange Server 2000 SP3 July 18, 2002
6.0.6396.1 Microsoft Exchange Server 2000 post-SP3 March 2003
6.0.6487 Microsoft Exchange Server 2000 post-SP3 August 27, 2003
6.0.6556 Microsoft Exchange Server 2000 post-SP3 April 2004
6.0.6603.1 Microsoft Exchange Server 2000 post-SP3 August 16, 2004
6.0.6617.52 Microsoft Exchange Server 2000 post-SP3
with Security Update MS05-021 April 12, 2005

6.5.6944 Microsoft Exchange Server 2003 RTM October 2003
6.5.7226 Microsoft Exchange Server 2003 SP1 May 2004
6.5.7638 Microsoft Exchange Server 2003 SP2 October 19, 2005

July 7, 2011

Service - Browser

The browser has forced an election on network \Device\NetBT_Tcpip_{E5F369B3-DDBB-4D59-8BEF-DBC518B76FCE} because a master browser was stopped.

Try to fix by changing registry. Refer to http://support.microsoft.com/kb/135404

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="FALSE"
"MaintainServerList"="FALSE"

Firewall HTTP Proxy in non-transparent mode

http://kb.endian.com/entry/22/





You can let the browsers get the proxy configuration automatically. Only precondition is, that you roll out the browsers with "Auto-detect proxy settings" enabled, which is default for both Firefox and Internet Explorer.

If you use the DHCP server or DNS proxy (or both) of Endian Firewall, there is no more to do. Otherwise you have two possibilities to make your clients find the proxy configuration on Endian Firewall:
1. Add a hostname to your local DNS called "wpad" and make it point to the Endian Firewall. You then should be able to reach Endian Firewall by accessing http://wpad/, otherwise it will not work.
2. Add a custom option to your DHCP server in order to make it push the wpad url with the other DHCP information.
Example for ISC DHCP server:

Global option:

option wpad code 252 = text;

Option for each subnet configuration:

option wpad "http://YOUR_EFW_IP_ADDRESS/proxy.pac";

Replace YOUR_EFW_IP_ADDRESS with the zones respective IP address of your Endian Firewall.
Note: If you like to force your users to use the proxy, you need to block HTTP ports within the outgoing Proxy. Otherwise a user may disable the Proxy within his/her browser and simply go directly without being blocked.

June 10, 2011

Granular Recovery Technology (GRT)

An Exchange backup to disk/tape with the Granular Recovery Technology (GRT) enabled completes successfully but with an exception "The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items"


 

Problem


 

An Exchange backup to disk/tape with the Granular Recovery Technology (GRT) enabled completes successfully but with an exception "The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items"

Error


 

The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items. A backup was run, but you will not be able to restore individual items from this backup set

Solution


 


In Backup Exec 11.x/12.x Exchange GRT backups to disk/tape may complete successfully but the job log reports an exception as shown above. The backup job does not collect or display any GRT information.

If Backup Exec debugging is enabled while running the Exchange GRT backup, then the following messages are logged in the debug logs. Please refer the Related Documents section below for more information on how to enable the debugging.


The Backup Exec Job Engine debug log on the Backup Exec server reports the following error:
------------------------------------------------------------------------------------------------------------------------------
[2944] 09/08/08 09:48:59 Application server(Exchange.domain.local) supports PDI
[2944] 09/08/08 09:48:59 Querying PDI data store server(BEXEC) for PDI support.
[2944] 09/08/08 09:48:59 NDMPAgentConnector:SetupConnection(): Data Server = BEXEC
[2944] 09/08/08 09:48:59 Could not resolve the 'ndmp' service, error: 10109, using port 10000
[2944] 09/08/08 09:48:59 ndmpConnectEx: 'BEXEC' resolves to the local machine itself. So, we will try and connect to a loopback address ...
[2944] 09/08/08 09:48:59 ndmpConnectEx : Control Connection information: A connection was established between end-points 127.0.0.1:19585 and 127.0.0.1:10000.
[2944] 09/08/08 09:48:59 NDMP version 3 connection CONNECTED
[2944] 09/08/08 09:48:59 NDMPAgentConnector::AuthenticateClient(): Using SSPI authentication with SLA/DLA as a fallback
[2944] 09/08/08 09:48:59 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): Attempting SSPI authentication...
[2944] 09/08/08 09:48:59 NDMP_SSPI: InitializeSecurityContext status 0x00090312 in 0 out 53
[2944] 09/08/08 09:48:59 NDMP_SSPI: InitializeSecurityContext status 0x00000000 in 190 out 72
[2944] 09/08/08 09:48:59 NDMP_SSPI: client authenticated with server
[2944] 09/08/08 09:48:59 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): SSPI authentication success.
[2944] 09/08/08 09:48:59 Enabling Shared Buffers Connection type
[2944] 09/08/08 09:48:59 PDI data store server(BEXEC) does not support PDI
[2944] 09/08/08 09:48:59 @@@@@@@MyCloseSocket called with sockfd = 1576(0x628) retval = 0
-------------------------------------------------------------------------------------------------------------------------------------

the Backup Exec Remote Agent debug log on the Backup Exec server reports an error while loading Exchange related Backup Exec dll's (bedsxese.dll and bedsmbox.dll etc.)
------------------------------------------------------------------------------------------------------------------------------------
[0904] 07/31/08 20:16:23   loaded bedsxchg.dll
[0904] 07/31/08 20:16:23   bedsxese.dll could not be loaded: The specified module could not be found.
[0904] 07/31/08 20:16:23   bedsmbox.dll could not be loaded: The specified module could not be found.
[0904] 07/31/08 20:16:23   bedspush.dll could not be loaded: The specified module could not be found.
--------------------------------------------------------------------------------------------------------------------------------------

SOLUTION:

1. On the Backup Exec server download the "Dependency Walker" tool from the following link
http://www.dependencywalker.com/ 

2. Launch the "depends.exe" tool and click on "Open" under the File Menu as shown below:


3. Browse to the installation directory of Backup Exec and attempt to load the "BEDSXESE.DLL". The default installation directory for Backup Exec is "C:\Program Files\Symantec\Backup Exec".

4. The Dependency Walker console will log an exact error in red in the lower half of the console that will report why the "bedsxese.dll" could not be loaded.  The most common errors that may get reported are related to the MAPI32.dll being absent on the Backup Exec server or if present than an incorrect version may be available.
 

5. Attempt to resolve the error reported in the Dependency Walker, restart the Backup Exec services and then reattempt the backup.

Error message: "The redirector failed to determine the connection type"

http://support.microsoft.com/kb/315244

Often see the error on window xp.

May 26, 2011

How to remove autorun.inf

Using the RD command to process the folder

rd foldername /s /q

RMDIR [/S] [/Q] [drive:]path

RD [/S] [/Q] [drive:]path


 

/S Removes all directories and files in the specified directory

in addition to the directory itself. Used to remove a directory

tree.


 

/Q Quiet mode, do not ask if ok to remove a directory tree with /S

May 19, 2011

POPBeamer


 

PopBeamer is tool for resending/transferring email from POP3/IMAP to exchange server.

http://download.dataenter.co.at/ftp/demk/setup_popbeamer_32.exe


 

May 11, 2011

Logparser

logparser -i:w3c -o:CSV -q:on -iw:on "SELECT* FROM c:\log\name.log WHERE Recipient-Address like `address'" > name.csv


 

Download here: http://download.microsoft.com/download/f/f/1/ff1819f9-f702-48a5-bbc7-c9656bc74de8/LogParser.msi

May 3, 2011

Adobe License issue


 


 

http://kb2.adobe.com/cps/405/kb405970.html

April 2, 2011

DSQUERY export creation date

dsquery * domainroot -filter "(&(objectCategory=Person)(objectClass=User)(sAMAccountName=*))" -attr sAMAccountName whenCreated -limit 0 >C:\output.txt

February 13, 2011

Disabling services and protocol logging on exchange 2003 servers

Refer to http://www.tech-faq.com/disabling-services-and-protocol-logging-on-exchange-2003-servers.html

Server 2003 Services

Exchange Server 2003 uses a number of components, services, and processes that communicate between each other on the local computer and remote computers. The role of the Exchange server and the clients that it has to support determines which services are necessary and unnecessary on your front-end and back-end Exchange servers.

All unnecessary services can be disabled. The security of your Exchange Server 2003 system is enhanced when you disable unnecessary services on your Exchange server. Port attacks can no longer be preformed on the ports of disabled services.

The main factors to consider when you want to disable a service are listed here:

  • Determine if there are any components and processes that use the service.
  • Determine if there are any other services that are dependent on the service running.

Exchange Server 2003 services can be classified as follows:

  • Role-independent services
  • Services running on an Exchange 2003 front-end server
  • Services running on an Exchange 2003 back-end server

Role-Independent Exchange Services

Role-independent Exchange services are those services that are needed as determined by the role performed by the Exchange 2003 server. There are also services that are needed for the following functions to be performed:

  • Administer Exchange Server 2003.
  • Run Exchange Server 2003 Setup.
  • To maintain interoperability with previous versions of Exchange.
  • To perform routing of messages.

The following services are needed to run Exchange Server 2003 Setup. The services have to be installed and enabled:

  • SMTP service
  • NNTP service
  • World Wide Web Publishing Service
  • IIS Admin Service

Exchange Server 2003 by default disables a few services. The state of these services is though maintained if you enable the service, and then later perform an upgrade or reinstallation.

The services that Exchange Server 2003 by default disables are listed here:

  • NNTP service
  • Microsoft Exchange IMAP4 service
  • Microsoft Exchange POP3

The following services are needed to administer Exchange Server 2003. The services have to be installed and enabled:

  • Microsoft Exchange System Attendant service
  • Microsoft Exchange Management service
  • Windows Management Instrumentation service

The following services are needed to maintain interoperability with previous versions of Exchange:

  • Microsoft Exchange Event Service
  • Exchange MTA Stacks
  • Microsoft Exchange Site Replication Service

The following services are needed to enable Exchange Server 2003 to perform message routing functions:

  • Microsoft Exchange Routing Engine
  • SMTP service
  • IIS Admin Service

There are also a number of services that provide additional Exchange Server 2003 features:

  • World Wide Web Publishing Service
  • Microsoft Search

Services Running on an Exchange 2003 Front-end Server

The services listed here are required on an Exchange 2003 front-end server:

  • Microsoft Exchange Routing Engine; needed to enable Exchange to route messages.
  • IIS Admin Service; needed to enable Exchange routing functionality. The IIS Admin Service is dependent on the Microsoft Exchange Routing Engine.
  • IPSec services; these services are needed if you want to configure an IPSec filter on OWA servers. IPSec services provide security between clients and servers on TCP/IP networks.
  • World WideWeb Publishing Service; needed if you want clients to be able to access OWA or Outlook Mobile Access front-end servers.

You can disable the services listed here on an Exchange 2003 front-end server:

  • Microsoft Exchange IMAP4 service; only required if your server is configured for IMAP4 clients.
  • Microsoft Exchange POP3 service; only required if your server is configured for POP3 clients.
  • Microsoft Exchange Information Store service; because Exchange 2003 front-end server do not contain user mailboxes or public folders, you can disable this service.
  • NNTP service; needed only if newsgroup functionality is required.
  • Outlook Mobile Access server; can be disabled if you are not planning to use Outlook Mobile Access.
  • Microsoft Exchange System Attendant; if you are not planning to perform configuration changes to Exchange Server, then this service can be disabled as well.
  • Microsoft Exchange Management service; if you are not enabling the Message Tracking feature, then you can disable the Microsoft Exchange Management service. Bear in mind though that the service also enables you to use the user interface to configure which domain controller or global catalog server Exchange Server 2003 uses.
  • SMTP service; should be enabled only if the Exchange front-end server is configured to receive SMTP mail as a gateway or a front-end server for IMAP4 or POP3.

Services Running on an Exchange 2003 Back-end Server

The services listed here are required on an Exchange 2003 back-end server:

  • Microsoft Exchange Information; required because the server stores user mailboxes and public folders.
  • Microsoft Exchange Management service; if you are enabling the Message Tracking feature, you need to enable the Microsoft Exchange Management service.
  • Windows Management Instrumentation (WMI); this service is dependent on the Microsoft Exchange Management service and needs to be enabled.
  • Microsoft Exchange System Attendant; required to perform administrative tasks for Exchange Server 2003. The service is also needed for Exchange maintenance to be performed.
  • NTLM Security Support Provider; this service is dependent on Microsoft Exchange System Attendant and needs to be enabled.
  • Microsoft Exchange Routing Engine; needed to enable routing functionality between Exchange servers.
  • IIS Admin Service; needed by the Microsoft Exchange Routing Engine.
  • Microsoft Exchange SMTP; needed to transfer messages.
  • IPSec Services; required if you want to configure and deploy an IPSec policy on the server.
  • Exchange MTA Stacks; needed if you want to maintain interoperability with previous versions of Exchange.
  • World Wide Web Publishing Service; needed if you want to communicate with OWA or Outlook Mobile Access front-end servers.

You can disable the services listed here on an Exchange 2003 back-end server:

  • Microsoft Exchange IMAP4 service; only required if a front-end server is configured for IMAP4 access.
  • Microsoft Exchange POP3 service; only required if a front-end server is configured for POP3 access.
  • NNTP service; needed only if newsgroup functionality is required.
  • Microsoft Search service; can be disabled if you are not using full-text indexing of mailbox stores or public folder stores.
  • Microsoft Exchange Site Replication service; can be disabled if you do not require compatibility with previous versions of Exchange.
  • Microsoft Exchange Event Service; can be disabled if you do not require compatibility with previous versions of Exchange.

Understanding Protocol Logging

If you want to troubleshoot mail system protocol issues then you should enable and configure protocol logging. Protocol logging provides information on the message commands that a user sends to an Exchange Server 2003 server.

This includes the following information:

  • Date and time
  • Protocol
  • Domain name
  • IP address
  • Bytes sent

The following Internet protocols can be configured to track the message commands that a user sends to an Exchange Server 2003 server.

  • SMTP
  • NNTP
  • HTTP

Protocol logs are stored in the C:WINNTSystem32LogFiles directory by default.

You can configure the logging format that should be used for logging the information:

  • ASCII-based format
  • Open Database Connectivity (ODBC) format

The different ASCII format options which you can choose between are:

  • Microsoft IIS log file format
  • NCSA log file format
  • W3C Extended log file format

For the ODBC format, you have to configure which ODBC database to use, and then configure the database to receive protocol logging information. You can use Access or SQL Server to create an ODBC database. The table in the ODBC database has to contain a set number of fields. The fields that have to be created are listed below. Bear in mind that varchar(255) in Access is the same as a Text data type with a Field Size setting of 255:

  • ClientHost field; varchar(255) data type
  • Username field; varchar(255) data type
  • LogTime field; datetime data type
  • Service field; varchar(255) data type
  • Machine field; varchar(255) data type
  • ServerIP field; varchar(50) data type
  • ProcessingTime field; integer data type
  • BytesRecvd field; integer data type
  • BytesSent field; integer data type
  • ServiceStatus field; integer data type
  • Win32Status field; integer data type
  • Operation field; varchar(255) data type
  • Target field; varchar(255) data type
  • Parameters field; varchar(255)

How to enable protocol logging for an SMTP virtual server

  • Open Exchange System Manager.
  • Expand the Administrative Groups node, the administrative group, the Servers node, Server Name, Protocols.
  • Expand the SMTP folder.
  • Right-click Default SMTP Virtual Server and then select Properties.
  • The Default SMTP Virtual Server Properties dialog box opens.
  • Select the Enable logging checkbox on the General tab.
  • Choose either of the following logging format options available in the Active Log Format drop-down list:
    • Microsoft IIS Log File Format
    • NCSA Common Log File Format
    • ODBC Logging
    • W3C Extended Log File Format
  • Click Properties.
  • The Logging Properties dialog box opens.
  • In the New Log Schedule area of the General tab, choose either of the following options:
    • Hourly
    • Daily
    • Weekly
    • Monthly
    • Unlimited File Size
    • When File Size Reaches, and set the size setting.
  • In the Log File Directory box of the General tab, set the log file location.
  • If you have selected the W3C Extended Log File Format option, then you can click the Advanced tab to configure the items which should be tracked.
  • Click OK in the Logging Properties dialog box.
  • Click OK in the Default SMTP Virtual Server Properties dialog box.

How to enable and configure logging on the Default HTTP virtual server

  • Open the IIS Manager console.
  • Expand the Web Sites node.
  • Right-click Default Web Site and then select Properties from the shortcut menu.
  • Click the Web Site tab.
  • Check the Enable Logging checkbox.
  • Select the log file format from the Active Log Format drop-down list. The default format specified is W3C Extended Log File Format.
  • Click Properties.
  • The Logging Properties dialog box opens./li>
  • On the General tab, set the following:
    • Specify when information should be saved to the log file.
    • Specify the log file size.
    • Specify the log file location.
  • Click the Advanced tab if you have selected the W3C Extended Log File Format. This is where you can configure Extended Logging Options.
  • Click OK in the Logging Properties dialog box.
  • Click OK in the Default Web Site Properties dialog box.

February 11, 2011

Tune-up Firefox

Start firefox
In address bar type "about:config"
Find out browser.sessionhistory.max_entries and change value from 50 to 5
Insert new key config.trim_on_minimize and select True
Restart the firefox.

WOW!!! Solved my problem as consume memory on firefox software

BSOD: Stop 0x0000007B

Yesterday, I got BSOD on LAPTOP computer and I found solution on Microsoft website which 2 links below

http://support.microsoft.com/kb/324103
Advanced troubleshooting for "Stop 0x0000007B" errors in Windows XP

http://support.microsoft.com/kb/307545
How to recover from a corrupted registry that prevents Windows XP from starting

After trying and wasting time to reboot the server. 2 things should be solution.
1. Check Hard disk setup on your BIOS
2. Restore registry from last time work.

----------------------------
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
---------------------------

How to edit PDF file?


This will show how to edit PDF file via Adobe Standard version 9.4.1.

Tool > Advance Editing > Touch up Text Tool

See the simulation..

February 8, 2011

Network card problem



Solution:

replace NDIS.SYS file on C:\WINDOWS\system32\drivers

January 24, 2011

Change the PDF/A viewing mode

PDF/A is an ISO standard for PDFs. Documents you scan to PDF are PDF/A-compliant. You can specify whether you want to view documents in this viewing mode.
In the Preferences dialog box under Categories, select Documents.
Choose an option for View Documents In PDF/A Mode: Never, or Only For PDF/A Documents.
You can switch in or out of PDF/A viewing mode by changing this preference setting again.



http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS3E0E8467-B787-4020-A1D3-6BC762A42DF2.w.html







January 18, 2011

How to Slipstream or Integrate Microsoft Office 2007 Service Pack (SP1 and SP2)

  1. Extract and copy the contents of the Office 2007 RTM (or Office 2007 SP1 if want to apply SP2) image or disc to a temporary folder.

    For example, C:\Office2007.

  2. Download or copy the Office 2007 SP1 Update file or Office 2007 SP2 Update file to another temporary folder.

    For example, C:\Office2007SP1 (office2007sp1-kb936982-fullfile-en-us.exe) or C:\Office2007SP2.

  3. Open a command prompt, and run the following command to retrieve and get the Office 2007 SP update MSP:

    C:\Office2007SP1\office2007sp1-kb936982-fullfile-en-us.exe /extract:C:\Office2007\Updates\

    Note: The drive letters, folder names and the service pack file names (name for SP1 and SP1 is different) may vary according to your own preferences.

  4. Accept the Microsoft Software License Terms to start integrating the service pack to Office 2007 installation files. The process will expand several .msp files to "Updates" folder.
  5. Optionally, uses disc image manipulation programs to re-create a fresh Office 2007 SP1/SP2 ISO image, or burn the Office 2007 SP1/SP2 installation files inside C:\Office2007 folder to a disc media with disk burning software.

January 10, 2011

Office 2007 upgrade fail ( code 2908 and code 1935)

---------------------------

Setup

---------------------------

Error 2908. An internal error has occurred. ({371F4B83-759A-4574-855F-DE18A63573F1} ) Contact Microsoft Product Support Services

(PSS) for assistance. For information about how to contact PSS, see C:\DOCUME~1\ADMINI~1.RM\LOCALS~1\Temp\Setup00000ed8\PSS10R.CHM.

---------------------------

Abort Retry Ignore

---------------------------


 


 

Error 1935. An error occurred during the installation of assembly


 


 


 

Unregister and then reregister Windows Installer

This action corrects most situations. Additionally, this action does not affect any currently installed programs that use the Windows Installer.


 

1. Unregister Windows Installer. To do this, click Start, click Run, type msiexec /unregister in the Open box, and then click OK.

2. Reregister Windows Installer. To do this, click click Start, click Run, type msiexec /regserver in the Open box, and then click OK.


 

Solution:

http://download1us.softpedia.com/dl/ba5479dd64ec859c43f3547d8f128cce/4d2a9456/100116561/software/tweak/dotnetfx_cleanup_tool.zip