Is there another way to access a newly created portal?

Currently, we add an application to the website in IIS, naming it something like mySite. Then, we create the portal with the alias xx.xx.xxx.xxx/mySite, where the x's represent the IP address. Finally, we can access the new portal by typing the alias in the browser address bar: xx.xx.xxx.xxx/mySite. We use this alias until the site goes live. Then, we change the alias to www.mySite.com and delete the website application.

The problem is that the website applications are triggering all of the scheduled tasks to run multiple instances. For example, if the standard DNN Search Engine Scheduler is supposed to execute at noon, 3 to 5 instances of the Search Engine Scheduler will execute at noon. The more website applications we have, the more multiple tasks there are (although the relationship is not one to one). When there are too many instances of the scheduled tasks, there are Scheduler Exceptions in the error logs.

I described this problem in more detail in a different thread: http://www.dotnetnuke.com/Resources/Forums/forumid/108/postid/380665/scope/posts.aspx#380665
(We are using DNN version 05.06.03. It is not a web farm or a web garden. However, when we edit a scheduled task, there is a checkbox list under the Run on Servers section.)

If there is another way to access new portals, then we can delete the website applications and hopefully eliminate the problem of scheduled tasks running multiple instances. Please advise.

Mary,

The DataSprings blog link you referenced was a case I worked on. From the other post it looks like you're still configured to have multiple IIS applications pointing to the same code base. This is going to cause a problem as all the sites point to the same database, but have a different IWAM path. This makes DNN think there are additional instances (because there are), and will cause the scheduler service to execute the processes on all instances. How many entries are there currently in your WebServers table in the DNN database?