Windows Admin Blog

What is MAPI(Messaging Application Programming Interface)

Messaging Application Programming Interface (MAPI) is a messaging architecture and a Component Object Model based API for Microsoft Windows. MAPI allows client programs to become (e-mail) messaging-enabled, -aware, or -based by calling MAPI subsystem routines that interface with certain messaging servers. While MAPI is designed to be independent of the protocol, it is usually used with MAPI/RPC, the proprietary protocol that Microsoft Outlook uses to communicate with Microsoft Exchange.

More on Wikipedia :http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface

How to Migrate/move SharePoint Databases from One SQL Server to Another

Following are the major steps to be taken to migrate/move sharepoint database from one SQL server to another SQL server:

1.Log into administration site (http://sharepointserver/default.aspx)
2.Click on the Operations tab and select perform a backup.
3.Select farm level backup and hit continue.
4.Enter destination of backup files and wait until finished backup.
5.Log onto the SharePoint server hosting the central administration.
6.Go to Start > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard.
7.Disconnect the server from the farm.
8.Repeat this step for the other web servers in the server farm if any.
9.Return to the first server and run the configuration wizard again, this time creating a new farm.
10.Enter data for the new database server (DBSERVER\Sharepoint) and create the farm.
11.Go to remaining web servers and join an existing farm using (DBSERVER\Sharepoint) for database.
12.Connect to administration site (http://sharepointserver/default.aspx)
13.Go to operations tab and select services on server.
14.Enable Office SharePoint Server Search
15.Enable Windows SharePoint Services Search Service (Leave default database information).
16.Go to Operations tab and perform a restore.
17.Select location of backup file and choose to restore the entire farm.

SCCM client push installation not working

When an SCCM client push installation is not working......we need to look at root cause of the issue. Here are some pointers may be helpful to you:

- Troubleshooting SCCM Client Push Installation issues
- http://social.technet.microsoft.com/forums/en-US/configmgrsetup/thread/78345405-4e92-4f25-820d-32df8b37307d/

Troubleshooting SCCM Client Push Installation issues

We come across many issues with SCCM client push installation and sometimes it takes lot of time to find a clue about the causes of the issues. Microsoft has recently releases a KB article which covers all possible solutions related to SCCM client push installation.

Here is the URL: http://support.microsoft.com/default.aspx?scid=kb;EN-US;925282

The ConfigMgr Advanced Client rejected the site server signing certificate

Error messgae “The ConfigMgr Advanced Client rejected the site server signing certificate to a trust-related failure (0x800b0109)” is showing up on few clients which are failing to install the certificate from the enterprise root CA.

Solution :
Compare the following registry values between a working and a failing client. If the values are different, replace the values on the bad machine with those from the good machine and re-install the client:

X64 – HKLM\Software\WOW6432Node\Microsoft\CCM\Security
X86 – HKLM\Software\Microsoft\CCM\Security
Keys - AllowedRootCAHashCode, Signing Certificate.

This may be helpful as well: Renewing or Changing the Site Server Signing Certificate

This posting is provided “AS IS” with no warranties and confers no rights.

Old versions of software and applications

Here are some cool site from where you can download old versions of softwares and applications :

http://www.oldapps.com/
http://www.oldversion.com/
http://www.versiondownload.com/
http://www.oldware.org/
http://www.321download.com/LastFreeware/index.html
http://www.downloadoldversion.com/

How to use SBMERGE command to update a Thinapp package

Here are the simple steps for using SBMERGE command on a ThinApp Project...

SBMERGE Process:

Make a copy of the original ThinApp Project WITH the BIN folder and it's contents (EXEs/Data Container).
Clear the SANDBOX within the %APPDATA%\THINSTALL folder.
Run the virtual application in the project to be updated.
Update the application with plugins, settings, updates, modifications. Close the app.
Re-launch the app and test the updates exist and work.
Close the app.
Open CMD and change to the directory where virtual application is stored.
Example: C:\Thinapp\packages\Firefox
Type "SBMERGE APPLY"
NOTE: If successful, the ThinApp Sandbox for this packaged app will have been removed from %APPDATA%\Thinstall.
Execute BUILD.BAT within the project just updated by SBMERGE.
Run new version of ThinApp packaged app to test updates/mods.
Deploy via AppSync, Side-by-Side, MSI (via ESD), etc.

Source: VMware
More on updating ThiApp packages: http://blogs.vmware.com/thinapp/2010/05/thinapp-updating.html