How to perform a clean boot in Windows XP

Over time, my computer getting slower on starting up. Happen to find this command MSConfig to the rescue.

How to perform a clean boot in Windows XP: "How to perform a clean boot in Windows XP
Note You must be logged on as an administrator or a member of the Administrators group to follow these steps. If your computer is connected to a network, network policy settings may also prevent you from follow these steps. 1.Click Start, click Run, type msconfig in the Open box, and then click OK.
2.On the General tab, click Selective Startup, and then clear the Process System.ini File, Process WIn.ini File, and Load Startup Items check boxes. You cannot clear the Use Original Boot.ini check box.
3.On the Services tab, select the Hide All Microsoft Services check box, and then click Disable All.
4.Click OK, and then click Restart to restart your computer.
5.After Windows starts, determine whether the symptoms still occur.

Note Look closely at the General tab to make sure that the check boxes that you cleared are still cleared. Continue to step 6 if none of the check boxes are selected. If the Load System Services check box is the only disabled check box, your computer is not clean-booted. If additional check boxes are disabled and the issue is not resolved, you may require help from the manufacturer of the program that places a check mark back in Msconfig.

If none of the check boxes are selected, and the issue is not resolved, you may have to repeat steps 1 through 5, but you may also have to clear the Load System Services check box on the General tab. This temporarily disables Microsoft services (such as, Networking, Plug and Play, Event Logging, and Error Reporting) and permanently deletes all restore points for the System Restore utility. Do not do this if you want to retain your restore points for System Restore or if you must use a Microsoft service to test the issue.
6.Click Start, click Run, type msconfig in the Open box"

Stealth Server (DNS)

Chapter 1. Introduction: "You can list servers in the zone's top-level NS records that are not in the parent's NS delegation, but you cannot list servers in the parent's delegation that are not present at the zone's top level."

- the beauty of flawless logic and phrase.

WMI useful sites for beginner

Microsoft - Introduction to Windows Script Technologies

WMI and VBScript for Microsoft Operating Systems

Automating SQL Server Management with WMI (Part 1)
(there are 5 parts in total)

SQL Server Scripting and WMI

This should get me busy this Saturday.

Windows Keyboard Shortcuts

Not really have much fun with the touch pad (or 'nipple') of the laptop I am using.
The best hotkey stokes of all are:
Run Dialog WIN + R
Minimize All WIN + M
Undo Minimize All SHIFT - WIN + M
Explorer WIN + E

BizTalk Server 2004 Setup/Architecture

Stand-Alone Instance(s)
http://geekswithblogs.net/mhamilton/articles/37527.aspx

Multiple Computers (Domain)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_depl_config_dibn.asp

Build a Windows Server Farm with Virtual Server 2005 (Observation)

Got a Dell PowerEdge 6350 Server with dual CPU (550 MHz/512), 4Gb Ram from eBay recently. The idea is to create a development/testing environment that simulates an online transaction environment using this server machine. I install Windows 20003 server (W2K3) on the physical machine, then use Microsoft Virtual Server 2005 to host a number of guest server OS.

A Windows 2000 server (W2K) is acted as domain controller (DC). I use a spare laptop for this to avoid the chicken and egg problem (I will come to the point later). I found Daniel Petri has a very useful step by step guide on how to configure domain controller.

All goes well until I accidentally tripped the charger and knocked the laptop to the ground. Fortunately my boss ‘lent’ me another laptop (PII 550MHz, 192Mb RAM). So I could reinstall the DC and have host and guest OS removed and rejoin the domain.

In retrospective of the entire exercise, I have following points.

1 CPU Consideration
Virtual Server 2005 masks actual hardware and simulates an IDE desktop machine with single CPU. So the using this Dell machine gains benefit by balancing guest OS processes weight across the two CPUs. A specific guest OS always runs on a single CPU.

This becomes a problem if install w2k3 as a guest OS. As the hardware concerned, a single CPU emulation environment does not meet the minimum hardware requirements for W2K3. In fact, the installation process taking so long that I have to abort it.

Nevertheless, having W2K3 as host OS is fine, because it can fully exploit both CPUs’ capacity. (MS Virtual Server 2005 is compatible with W2K3 only).

2 Virtual Hard Drive
To preserve the hard drive space, I use ‘Differencing Virtual Hard Disk’. The first thing after starting a guest OS that is built on child virtual hard disk is to use Microsoft sysprep tool to gain a new system identity.

In retrospective, I should have made the parent virtual hard disk bigger. Child disk is sized based on the size of the parent’s. So if parent disk is 3Gb, child disk is also 3Gb. The W2K OS takes about 2Gb space. After running sysprep on child disk, it’s vhd file dynamically grows to 1.2Gb – not a lot of space remained.

In this situation you can attach a secondary virtual hard drive to the guest OS in question. It is just convenient to have a bigger primary drive in situations that windows installation can go into the default ‘C:\Program Files’ folder.

3 Network Interface Card (NICs) and connections
The Dell server comes with two NICs and two onboard NICs (not used at the moment). To maximum performance throughput they are configured as:

Card 1/Connection 1 is dedicated to the guest virtual network. So all guest OS will use this NIC to participate the domain network. On host OS, all network protocols bind to this NIC removed and leave only virtual machine network services checked. On each guest OS TCP/IP protocols is bound and assigned unique static IP addresses.

Card 2/Connection 2 is designed for handling network traffic of the host server. It TCP/IP protocols enabled but virtual machine network services unbind.

Connection 3 is a loop-back adapter for handling file sharing and other network traffic between guest and host systems without having them travel externally.

Connection 1 and 3 needed to be added to the virtual server to create two virtual networks (Note 1). Also check Note 2 on how to configure loop-back adapter for file sharing, or Host-Guest network traffic.

Virtual server emulates these NIC/connections in the guest systems. In my configuration, they all called ‘Intel 21140 Based PCI Fast Ethernet Adapter’. Virtual server generates a dynamic MAC address for each NIC on each guest OS (Note 3). This is of course different from the physical MAC address.

It is very easy to confuse on which NIC is for what purpose. So I would suggest make a note on the dynamic MAC addresses before configuring the TCP/IP protocols in the guest OS.

If more NICs are added via Virtual Server Administration website, on guest OS you can run hardware scan/update to pick them up like you will normally do on real machine.

4 Domain Controllers
There are a few options available when comes to where to place the domain controller in this garage network. Microsoft’s Running a Domain Controller in Virtual Server 2005 gives a step-by-step guide on network planning for virtual servers environment with following scenario.
1) Domain controller on host OS, application servers on guest OS.
2) Domain controller on guest OS, application servers on host OS.
3) Both domain controller and application servers are on guest OS.

The article gives credits to solution 3. It creates a pure virtual network. It has a clear defined network boundary with performance consideration.

In my opinion, solution 1 degrades the virtual server performance. Virtual server required IIS 6 to be running for administration via a web site. Having domain controller and IIS running on same server degrades IIS.

Solution 2 has application servers on host OS. Excuse me, but having guest OS running application server is you want originally, isn’t it?

There is also a chicken and Egg problem. Solution 2 and 3 requires to have domain controller installed on a guest OS. This is not a very option for my situation. The Dell server is placed in the conservatory and accessed via remote desktop (terminal services in admin mode) connection from the study room over a wireless connection.

If I install the DC in a virtual server, I must stay in the conservatory and wait for the host to boot-up, launch the guest OS (can set it to launch automatically though). Host server cannot participate in this domain. Which may cause problems in the future, for instance, file sharing issue when required to configure more virtual machines; or if the virtual network requires a W2K3 server – such like Microsoft BizTalk Business Activity Service Monitoring. BAS requires SharePoint services. And SharePoint can only deployment on W2K3.

So I decide to configure an old laptop as a DC and reducing a guest OS from the virtual server. This helps to off-load some CPU and memory load from the host as well. It looked like this:

5 Virtual Server Administration Website user authentication
The issue discussed here need to re-apply if the host/guest OS have their domain membership changed (Note 4).

On access the VS admin site, it is likely you will be challenged by an Internet security pop-out window or the website will prompt you for valid credentials. If you are sure the username and password are correct and it is not accepted, it is likely that the user is not grant access to the admin website.

There are two things here. First, we should allow IE send the NT credentials automatically. Then we need to grant user access to the virtual server admin site.

1) Add the admin site to Local Intranet category via Internet Options Security tab. Then click the ‘Custom Level…’ button on the security tab. Security Setting window pops out. Scroll to the bottom of the settings, there is an option – ‘User Authentication Logon’. Make sure it is ‘Automatically logon only in Intranet Zone’ or ‘automatically logon with current username and password’ selected.

2) Browse to the admin site, logon as a local administrator. Click on Virtual Server Server Properties on left navigation column, then click on ‘Virtual Server Security’. Then add domain users to the list.

6 Terminal Services and Remote Access
Normally you will access guest OS via remote desktop connection. This is supported by terminal services on W2K3 and W2K server (Note 5).
Again, the issue discussed here need to re-apply if the host/guest OS have their domain membership changed.

The problem occurs when you remote access guest OS with a non-administrator NT account and on successful login it display this error message: ‘You Do Not Have Access to Logon to This Session’ and you are thrown out.

To get over this problem, you need to grant remote access permission to the users/groups via Terminal Services Configuration on each guest OS.

For detail see Microsoft knowledge base article 224395.

Note 1 This is done via virtual server administration website). There should an existing one: ‘Internal Virtual Network’ which deploys DHCP and enable virtual machines to see each other.

Note 2 Loop-back adapter configuration (from Virtual Server 2005 accompanied guide vs.chm)

1. On the host operating system, open Network Connections, right-click the local
area connection for Microsoft Loopback Adapter, and then select Properties.
2. In the Microsoft Loopback Adapter Properties dialog box, verify that the
Virtual Machine Network services check box is selected.
3. Click Internet
Protocol (TCP/IP), and then click Properties.
4. On the General tab, click
Use the following IP address, and then type the IP address and subnet mask (such
as 192.168.1.1 and 255.255.255.0).

Important
You can use any
Transmission Control Protocol/Internet Protocol (TCP/IP) address, but it is best
to choose one from a reserved range of non-routable TCP/IP addresses. For
example, TCP/IP addresses of the form 192.168.x.y, where x is a value from 0
through 255 and y is a value from 1 through 254, are non-routable. The value you
choose for x must be the same on the host operating system and each guest
operating system that is to be part of this virtual network. If your primary
Ethernet connection uses one of these non-routable addresses, you must choose a
different value for x to assign to Microsoft Loopback Adapter.
5. Click OK,
and then click Close.
Notes
· To perform this procedure, you must be an
administrator or a member of the Administrators group.
· To set up multiple
network connections using Microsoft Loopback Adapter, use different subnets.
· Do not set a value for Default gateway.

Note 3 The dynamic MAC addresses for a guest OS can be found from its configuration page on the Virtual Server Administration website, then follow the link ‘Network Adapters’.

Note 4 In my case, the domain controller was unrecoverable and has to be reinstalled and configured on a replacement laptop. Though I use the same domain name, active directory is essentially different from the previous one. So all domain members need to drop their existing memberships and rejoin the domain.

Note 5 You need to obtain license if use terminal service in application mode. For use it in administration mode you don’t need license and can have up to two concurrent connections.

Forgot the Administrator password

Shit can happen and it will always happen on an unexpected time. Such like forget your administrator password (what could be worst after a two’s holiday?)

Daniel Petri introduces a useful tick on reset the LOCAL Administrator password. The trick is to force launch a command line console window into the misfortune OS and reset the admin password before hit the ‘CTRL+ALT+DEL’. To do so, you need to fool the start-up process to use CMD.exe instead of logon.scr as the screen saver.

This is not to be confused with reset DOMAIN Administrator password. It follows a similar method to force into the system and therefore reset the password on the domain controller. The addition is that you need to create an Offline NT Password & Registry Editor boot disk so that you can local(offline) login to the domain controller machine.

I haven’t tried neither of them yet. Who knows, I am the admin of my home web farm and I may go for a cross-land tour.

Biztalk Resource:

Valuble Biztalk Resource:
Biztalk MessageBox Advance Queries

BizTalk FAQ

I am working on a Biztalk POC project at the moment, here is a list of problems have occurred to me at varuious stage and the solutions. The list will keep growing as proceeding.

1. Biztalk Message Queue causes conflict with MSMQ
-- In short, you cannot run MSMQT on the same machine as MSMQ runs. What behind MSMQT is MSMQ, they are using the same port (1801). This can happen on the test/deployment machine if MSMQ already run then you configure to use MSMQT. This problem raised when you try to start Biztalk Application again.. Stop the MSMQ service (Message Queuing and Message Queuing Triger) from Service Control Console, then start the Biztalk Application will fix the problem.

2. Running an independet web service on the same development machine that has biztalk server and Sharepoint server installed. I was getting 404 'file not found' when requesting a web service.
--MS Development team suggest the stsfltr.dll ISAPI filter from sharepoint team services may cause the problem. I have tried remove this ISAP filter from IIS, problem solved. Read this KB

3. I drop the request xml into the receive port-bound dir, it has been processed but the resulted xml doc is not produced, why?
-- It is spot on that orchestration process picks up the request as it has been removed from receive port-bound dir. The first thing to check is the send port - outbound settings. Is the dir granted with appropriate write/modify access to the account that BiztalkServerApplication runs under? Is there any typo in the address URL send ports point to?
If you are using late bound, the problem is easy to rectify. Just stop the orchestration process, unlist it, correct the problem and restart the orchestration process- make sure all receive and send ports and enabled/started.
If the application is bound at the design time, there are few more things need to be done.
First on the development pc, open the source project, correct the problems and rebuild it.
Then on the deployment server, stop/unlist the problematic orchestration from the Biztalk admin console.
Then start the deploy wizard, remove the problematic biztalk assembly from the configuration database-you need to remove it from GAC as well.
Install the new compiled biztalk assembly.
Specify all late bind ports to the new orchestration process use Biztalk Explorer.
Enlist and start the orchestration process from Biztalk Admin console

Lesson learn: Always use late binding ports when permitted.

CMS SCA Host Headers Mapping vs IIS HTTP Host Headers Mapping

MCMS Server Configuration Application (SCA) has an option to map channel names to host headers names. It can be used to allow host multiple CMS web sites with different domain names on the same CMS server.
To do this, we need to map top-level channels as the root channels for a URL with a host header name that is identical to the channel name. When CMS generates a URL pointing to an item inside the virtual site www.CMSsite1.com, it prefixes the URL with the name of the channels in which it is contained.’ See chapter 18 of book Microsoft Content Management Server 2002
There are two points need to note:
1. Names of top channels on a CMS server must match the virtual site names in IIS.
2. The virtual site names must be valid DNS name.

So a typical co-hosting configuration for three web applications on a development box can be:

In MCMS Site Manager:
We have three top channels, they sharing the same CMS database, and named as:
www.CMSsite1.com
-------------Product
-------------Service
www.CMSsite2.com
-------------AboutUs
-------------OnlineShopping
www.CMSsite3.com
…

Install a network loopback adapter and assign IP address from 192.168.2.1- 192.168.2.3

In IIS Manger, create three web applications named and assign IP address as:
www.CMSsite1.com (192.168.2.1)
www.CMSsite2.com (192.168.2.2)
www.CMSsite3.com (192.168.2.3)

Open %Winnt%\system32\drivers\etc\host with notepad and add following entries:
192.168.2.1 www.CMSsite1.com
192.168.2.2 www.CMSsite2.com
192.168.2.3 www.CMSsite3.com

So you may ask how will this related to HTTP host header mapping in IIS?
Not a lot. IIS HTTP host header mapping is used to provide multiple-hosting. The HTTP host headers identify multiple virtual web sites that reside on one physical server and all sites shares same IP address.
However, you need to configure the HTPP host headers on the IIS site if a single IP address is used for multiple CMS sites.

Remember to Map CMS Vitual Directory

Here is the story:
VS.NET by default uses localhost:80 (default web application/VS.Net Solution Host) to publish CMS App, say http://localhost:80/myCmsApp1. I create a Web app using a different IP address which maps to http://localhost:80/myCmsApp1. However, I forgot to create a CMS VD from within
myCmsApp because it has IIS root with mapping to CMS already - multi web apps sharing one IP.
It looked like this:
http://MyIIS/myCmsApp1
/myCmsApp2
/cms

Now it needs a http://MyIIS/myCmsApp1/cms that maps to (...)\Program Files\Microsoft Content Management Server\Server\IIS_CMS to work correctly from within localhost, otherwise you may get some funny client broswer script errors like the following:

Line : 447
Char :4
Error : Type mismatch: "Initialize Toolbar"
Code:0
URL: http://myCmsApp1/NR/exeres/[Guid],frameless.htm?NRMODE=Unpublished&NRTEMPLATEVERSION=CheckedOut&WBCMODE=AuthoringReedit

placeholder icons may not be displayed correctly as well as Web Author console not functioning.

Create an CMS VD in myCmsApp1 to solve the problem.

CMS, work with template gallery in VS.NET

Symptom 1: On Loading Woodgrovenet.sln to VS.NET, there is complain: "Could not get the root template gallery"

Error message: The windows credentials provided could not be validated.

Reason: The user running Microsoft Visual Studio .NET is not in a Template Designer role or their role does not have access to the root template gallery. So need to run Site manager to add the current logon account as a Template Designer.

Symptom 2: Cannot modify Template Gallery Item
I am logon to NT and start a new CMS Web project with VS.NET. The NT logon I used was granted as Template Designer. I can see the whole project but cannot add/modify template gallery items.
Double check the Template Designer rights, found there isn’t Group rights granted to the project-top channel-http host header (same name).
After grant the rights explicitly, I can now Add/modify TGI in VS.NET.

Accessing CMS sites off a root URL by sharing IP address and port number

In this scenario, we have a root IIS site and multiple CMS web application off this root on a development environment. Instead of configuring each into their own CMS environments, they share a same CMS db, users/roles scheme. So developers can easily switch between sites

The site structure looked like this:
http://mycms --IIS root
--WoodgroveNet --CMS –enable web app 1
--PetshopCom --CMS –enable web app 2
--WoodwidgetOrg --CMS –enable web app 3

Instead of accessing each by:
http://mycms/WoodgroveNet
http://mycms/PetshopCom
http://mycms/WoodwidgetOrg

We want:
http://WoodgroveNet
http://PetshopCom
http://WoodwidgetOrg

Here is how to achieve this:
Step 1. Make mycms CMS enabled
You can use MCMS SCA tool to assign read/write rights or manually map these virtual directories:
- NR((MCMS installation drive)\Program Files\Server\IIS_NR)
- MCMS((MCMS installation drive)\Program Files\Server\MCMS)
Copy ASP.NET Client API by run:
aspnet_regiis –c from the appropriate .Net framework directory. for v1.1 this is C:\WINNT\Microsoft.NET\Framework\v1.1.4322

You need to manually map IE Web Control API, SCA wouldn’t do it for you:
Create a virtual directory mycms/Webctrl_client that map to (IIS installation drive)\Inetpub\wwwroot\ webctrl_client

Step 2. Check and remove mycms Host Header Name if there is one.
In IIS Manager, mycms|properties(right click)|Web Site Tab Web Site Identification, click “Advanced”. Now into Advanced Multiple Web Site Configuration.
To remove it, select the entry then click “Edit”.

Step 3. Add multiple website.
Into Advanced Multiple Web Site Configuration, click on “Add”. Use the same IP address and Port you assign to mycms for WoodgroveNet, PetshopCom and WoodwidgetOrg.

Step 4. Update DNS hosts file
notepad c:\winnt\system32\drivers\etc\hosts
add this: mycms woodgrovenet PetshopCom WoodwidgetOrg
you should use the IP address you assign to mycms.

You are done.

Microsoft CMS2002 installation notes

Install on Windows 2000 with .Net Framework 1.1 and VS.Net 2003

• To install CMS2002 SP1A you need to install CMS2002.
• If CMS dev tool (VS.NET client) is desired, you cannot just install CMS2002 on top of VS.NET 2003. It complains ‘VS.NET is not found’, you need to install VS.NET, including ‘Windows Component Update’.
• Followed the CMS2002 installation guide.
• Apply SP1A.

Install on Windows 2003 Server
• Remember to check IIS and Server side includes have been installed.
• Apply high security template if you haven’t have .Net Framework or VS.NET install. This is the best opportunities to do so.
• No need for IIS LockDown, that is build-in to IIS 6 on Win2k3.
• Install VS.Net(2002) including ‘Windows Component Update’, if CMS 2002 DEV tool is desired. The dev plug-in only workes on VS.Net 2002.
There is a known issue that you need to enable ASP and FPSE on IIS. Follow this:
• Framework 1.1 is installed when installing Win2k3.

If loop-back adapter is used and MCMS SCA, Public, Authoring sites are configured to use a non-default IP address,i.e. localhost, remember to update your DNS host file, and set internet connection option to bypass local address.

Install sample site Woodgrove Bank
Installation gone through OK but I have problems on hitting the site.


The first problem is about running ASP.NET on a Domain Controller
The server I use is configured as a Domain Controller (with Active Directory) -- Windows 2000 Advanced Server, .NET 1.1. Error page like this:

Access to the path "C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\Woodgrove\9c4ac7bd\97d3c1c0\global.asax.xml" is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

This doc offers a solution:
FIX: ASP.NET Does Not Work with the Default ASPNET Account on a Domain Controller

In practice, I use IWAM_(MachineName), instead of ASPNET. All security policies (Domain Controller Security Policy, Domain Security Policy, Local Security Policy) needed to be update to include IWAM_(MachineName) for Log on as a batch job as pointed out in the above.
Then add IWAM_(MachineName) with full control to physical directory C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

Run iisreset.

Now I am getting a different error: missing SeImpersonatePrivilege

[COMException (0x80041b58)]
Microsoft.ContentManagement.Interop.Publishing.CmsHttpContextClass.Initialize(String currentUrl, String httpHostName, Int32 serverPort, Boolean isSecureServer, Int32 iisInstanceId, String remoteMachineAddress, String authenticationType, String authenticationToken, Int32 windowsUserHandle, String ClientAccountName) +0
Microsoft.ContentManagement.Publishing.CmsHttpContext.initialize(IntPtr windowsToken, String cmsAuthToken, String clientUserName, String clientAccountType) +297
Microsoft.ContentManagement.Publishing.CmsHttpContext.getCmsHttpContextFromIdentity(HttpContext httpContext) +1088
Microsoft.ContentManagement.Publishing.CmsHttpContext.get_Current() +57

As documented in CMS2002 SP1 MCMS 2002 - Debugging FAQ

The Account (IWAM_(MachineName) running the ASPNET_WP worker process is missing the SeImpersonatePrivilege privilege when Windows 2000 SP4 is installed.
There are two steps to resolve this problem:
1) Adding impersonation privileges to IWAM_(MachineName) or any account (such like ASPNET) that runs ASPNET_WP worker process. This can be done by adding ‘Impersonate a client after authentication’ to the account in Local Security Settings. Check Microsoft Content Management Server 2002 Service Pack 1 Documentation.

2) Update Machine.config and/or web.config
(c:\WINNT\Microsoft.NET\Framework\{version number}\CONFIG\Machine.config)
As I am running .NET Framework 1.1 for this, I use version v1.1.4322.
Find the ProcessModel node and update the username, password attribute to be
<processModel [other attributes] userName="<domain Name>\IWAM_(machineName)" password="(actual password)"

Wahoo, this problem gone. Now I can see the Woodgrove initial login page, which prompts me for login credentials-a bit strange. It says:
You are using an insecure connection. If you click Continue it will be possible for others to view information you send or receive.

I try to login using a few different identity CMS_SYSTEM, NT accounts that has been grant Author role. I also use IIS console manager to check the properties- directory security to be anonymous/window authentication--seemed fine.
Then I look up the Web.config – notice the authentication mode has been set to ‘forms’ like this:

<authentication mode="Forms">
<forms name="WoodgroveNet" path="/" loginUrl="/WoodgroveNet/Templates/ManualLogin.aspx"
protection="All" timeout="30" >
</forms>
</authentication>
<authorization>
<allow users="*" />
</authorization>

I quickly comment out this and uncomment the Windows authentication mode
<authentication mode="Windows">

Finally got the site working!