H-Sphere Upgrade to 2.5 Patch 8 on Feb. 5th 2007

[admin]

At first we will have NT up to the latest NT server running asp.net 1.1 after the upgrade new servers will have ASP.NET 2.0 only thing we are going to do is move your site from an old server to a new server if you ask us to so that you can use asp.net 2.0. How you go about switching the code is 100% up to you.

If you want to put a single site there to setup the site(s) in asp.net 2.0 thats also fine and then just have that user removed when your done so we don't keep unneed account sitting around. I have not coded a single site in asp.net so how you get from 1.1 to 2.0 is not something we can help with we know the how to run the server not how to write the code or switch from 1.1 to 2.0 as far as code goes.

[Dabelo]

Brad -

I didn't mean to imply any responsibility on your part to do any site upgrading.

I wanted to point out that v1.1 sites mostly will not run on v2.0. and so
moving the site to the new server will require it to be upgraded off line.

This will result in additional site down time because you cannot run the
upgraded v2.0 site the old server, and under your plan, you cannot run
the site on the new server (configured for 2.0), after it is moved, but before it is upgraded. -- I.E. catch 22

What I am suggesting is

1. To get the site moved to a location on the new server that is configured
to run V1.1. for that site and thus allow the site to be up until after it
is upgraded without downtime.

2. Allow the owner to then upgrade (upload the v2.0 version) of the site
doing whatever he needs to do. That is his responsibility. At this time the
site would be down for a short time.

3. The owner would then submit a ticket to reconfigure IIS for that site to
be changed to v2.0, allowing the site to be functional again.


Step 3 is only because psoft v2.5 dosen't allow the owner to configure
IIS like v2.51/3.0 does.


This process would result in much less downtime for an existing site that is
to be moved.


Looking for your response _

Dabelo

[admin]

No way to do that in H-Sphere when we move the site from server 1 to server 2 it sets it to be deleted in 24 hours. Testing should be done off line anyway not on our live servers so the person could setup the site off line and get it ready then tell us to move the user and just upload the new site once the site is moved over.

Not sure how else to do it if you going from 1.1 to 2.0, we can't run the site on 2 servers, the only other way to do this like I said is setup a test users maybe to at least upload it and check that it works if so then move the user and upload the new site after its moved.

[soky]

Originally Posted by admin

Q: Will ASP.net 2.0 be supported?
A: Yes, asp.net will be available on all new servers installed; we plan to install a new Windows server within 7 days of completion of the upgrade. Current customers can asked to be moved to this server and new customers can ask to also be put on this system. It will be off for new signups at first but any can be moved to this if they plan to use .net 2.0.

I'm so happy I'm dancing
This is going to help me make some serious money!!!
I'm scheduling the week off that week. LOL
This is what I've been praying for!!!
It's time to PARTY!!!
I'll still be recovering from the Super Bowl parties anyway!!
Thanks guys!!! It's been a long time coming ( insert inappropriate flamo here)... I'm glad we are getting somewhere with this.
Next project? More dedicated servers!!

[admin]

lol

[powvex]

having php 4 & 5 on same server, same site, running on windows is possible, and as we know it doesn't matter which CP. you can have both running like .php file extensions for version 4 and .php5 for version 5. we have this on 4 of our win boxes simultaneously with no problem.
so what's wrong here for having them both?

[kattouf]

Nothing. As far as i know brad said we are having both..

[hex]

Originally Posted by powvex

having php 4 & 5 on same server, same site, running on windows is possible, and as we know it doesn't matter which CP. you can have both running like .php file extensions for version 4 and .php5 for version 5. we have this on 4 of our win boxes simultaneously with no problem.
so what's wrong here for having them both?

Yep. I'm trying to get a site going now that is going to need to use both php4 and php5 code (in different directories).

PHP is by design capable of supporting multiple versions.

[hex]

Actually I take that back. I'll be good with just php5 if need be. MediaWiki is the software package I need to install which needs php4. I thought vBulletin did not support php5 yet (which was a wrong assumption).

[admin]

Saturday February 3rd at 11am ET we will begin running check disk on 17 servers. This process will take 2 days, so please advise your customers now that this maintenance is scheduled. This process **will** take down sites for the duration of time that it takes for check disk to run on the affected servers.

Each server will take approximately 3 hours and we will be doing 3 servers, approximately every 3 hours during the hours of 11am & 11pm ET on Saturday, February 3rd and Sunday, February 4th.

Below you will find a list of the affected servers and the order in which they will be attended to:

Saturday, February 3rd

NT6, NT16, NT18: 11am - 3pm ET
NT19, NT20, NT22: 3pm – 6pm ET
NT23, NT27, NT42: 6pm – 9pm ET

Sunday February 4th

NT46, NT48, NT50: 11am – 3pm ET
CF3, NT10, NT21: 3pm – 6pm ET
NT29, NT36: 6pm – 9pm ET

**All times are approximate. While we are estimating check disk to complete in 3 hours, it may take longer on some servers.

**We will not be issuing downtime credits for any sites that experience downtime because they are located on the affected servers.

We appreciate your patience and cooperation.

[admin]

I also have more good news as well but I will save that until all of this is out of the way and it's 100% complete but it's something everyone should like. Lets keep it at that and everyone guessing.

[bootNumlock]

brad...

will the sites be offline for the entire 3 hours per box???

Just need to create a realistic expectation for my clients.

Thanks.

[commongenius]

Originally Posted by Dabelo

I wanted to point out that v1.1 sites mostly will not run on v2.0. and so
moving the site to the new server will require it to be upgraded off line.
This will result in additional site down time because you cannot run the
upgraded v2.0 site the old server, and under your plan, you cannot run
the site on the new server (configured for 2.0), after it is moved, but before it is upgraded. -- I.E. catch 22

This would only be true if the new servers will be configured with .NET 2.0 but NOT .NET 1.1. Is that the case? I cannot imagine why they would not have both.

Originally Posted by admin

...so we can up with just put 2.0 on all the new servers and make it the default and we can move customers around if they want 1.1 or 2.0 and will not cause as big of mess when we jump to .net 3.0 once psoft supports it.

".NET 3.0" is simply a new set of libraries, formerly known as WinFX. They use the existing framework version (.NET 2.0). Its no different than installing any set of third-party libraries. There is nothing for psoft or anyone else to support, so there is no reason for the new servers not to immediately have the .NET 3.0 libraries.

[kattouf]

Well i'm going to guess it might be related to this:

http://www.psoft.net/HSdocumentation...seller_support

I am looking forward to the new ticket system :-)

[Dabelo]

Originally Posted by commongenius

This would only be true if the new servers will be configured with .NET 2.0 but NOT .NET 1.1. Is that the case? I cannot imagine why they would not have both.
".NET 3.0" is simply a new set of libraries, formerly known as WinFX. They use the existing framework version (.NET 2.0). Its no different than installing any set of third-party libraries. There is nothing for psoft or anyone else to support, so there is no reason for the new servers not to immediately have the .NET 3.0 libraries.

In IIS there is a switch to configure the framework for a site to support v1.1 or v2.0; (This has nothing to do with the design of the site.)
Under psoft 2.50 this setting setting is not available in the control panel,
but must be configured manualy via a support ticket. (this is fixed in psoft 2.51/3.0) .
In my last two post to Brad in this thread, I tried to point out that by
default the a site that is requested to be moved to a server supporting
net 2.0 should have this setting set to v1.1 ON THE NEW SERVER as the
site is being moved, because the site that is being moved is still a net v1.1
site. AFTER the move is completed, the site owner can upgrade his site
to net v2.0, and then do a ticket request to change the IIS setting be for
V2.0.
As you can see in his responses, he missed the point completely, and is
insisting that the NEW servers be configured for Net 2.0 only.
I have given up on the point
_Dabelo