Re: Problems after upgrade

Yes process was as follows:
Original setup
SBS2000 PremEd with ISA2000 & SQL2000 installed with all possible updates
installed, on old hardware.

Aquired new hardware and latest upgrade media SBS2003 PremEd with SP1
slipstreamed (retail box version from distributor Synnex)

Performed swing migration to new hardware (Migrates AD)
Ran SBS setup which clean installs SBS components and Exchange, forklifted
in Exchange store. This all went as expected.
Clean installed SQL2004 and ISA2004
Ran To Dos from Server management.
Installed user apps and Data. Did data and application verification
including exchange store from server console.
Added static routes for subnets

Put server into place started discovering issues.

"Cris Hanna [SBS-MVP]" wrote:

> You say you installed SQL and ISA2004
> So do you have SBS 2003 Premium Edition?
> Did you do the ISA 2004 as a part of SBS SP1??
> Did you then re-run CEICW??
>
> --
> Cris Hanna [SBS-MVP]
> -----------------------------------------------
> Please do not contact me directly. Please only repond here in the newsgroup
> for the benefit of all.
> "Robert Ozone" <RobertOzone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:6159B043-C62B-4E8B-B52B-A8F15CFA1C9D@xxxxxxxxxxxxxxxx
> > Cris, Thanks for working with me I need help bad.
> >
> > Swing Method onto new hardware. That seemed to go well, that is the AD and
> > message store migrated cleanly.
> >
> > I then clean installed ISA2004 and SQL. I have had many problems since
> > that.
> > It seems the new ISA2004 is not cool with exsisting network topology.
> > The topology is:
> >
> > Internet-T1--router---(ext-SBS2003-Int)---VPN Router-T1 and DSL--remote
> > sites
> >
> > Server is 192.168.16.2
> > Sonicwall VPN router 192.168.16.1
> > Internal LAN is 192.168.16.X
> > Subnets are 192.168.17.0 thru 23.0
> >
> > It was working fine with SBS2000 & ISA2000. Just had to add static routes
> > for the subnets.
> >
> > All computers are either in the domain or a workgroup by the same name.
> > Prior to upgrade the all sites could see all computers and access shares
> > on
> > either domain computer or workgroup computers.
> >
> > Now the workgroup computers with shares are not recognozing the users
> > trying
> > to access shares. They are prompting them for user id and password.
> >
> > MAPI devices are no longer connecting says it can't find server.
> >
> > The remote web workplace for some users is logging in then immediatly
> > logging off.
> >
> > When the remote users login they got the internet options set to use proxy
> > server which I don't want to happen. From what I can tell, it is set based
> > on
> > the ISA2004 internal network definition. Anyway to manage this?
> >
> > Though some of these things should not be related to ISA2004. I am going
> > crazy with these issues while trying to solve the one major issue of the
> > long
> > login delay.
> >
> >
> > "Cris Hanna [SBS-MVP]" wrote:
> >
> >> OK
> >> How did you upgrade
> >> In place upgrade OR new server?
> >>
> >> --
> >> Cris Hanna [SBS-MVP]
> >> -----------------------------------------------
> >> Please do not contact me directly. Please only repond here in the
> >> newsgroup
> >> for the benefit of all.
> >> "Robert Ozone" <RobertOzone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:39DFEBBF-2CCC-4156-875B-E668EB2A45C7@xxxxxxxxxxxxxxxx
> >> >I just upgraded from sbs2000 prem ed to sbs2003 prem ed. I am now having
> >> >many
> >> > problems.
> >> > Network was working fine previously.
> >> >
> >> > 1. Users are experiencing very long long in time 5 to 10 minutes.
> >> >
> >> > 2. Unable to VPN anymore, can VPN successfully using administartor but
> >> > not
> >> > users using same connectiod. Is there a new group membership they need
> >> > to
> >> > be
> >> > in?
> >> >
> >> > 3. Outlook connection problems, had to set security tab to "password
> >> > authentication NTLM" to connect.
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Upgrading to SBS 2003
    ... My idea was to upgrade the hardware and install a proper server OS. ... SBS is a server O/S, ...
    (microsoft.public.windows.server.sbs)
  • Re: P4 Xeon compatibility with 5.0.5
    ... > I am looking to upgrade our current Pentium II 300 Mhz. server. ... Maybe you can find an old P3 desktop and transfer the special hardware ... what's mostly going bad on the old box are the hard drives and the ...
    (comp.unix.sco.misc)
  • Re: A difficult migration (2000 -> 2003)
    ... > I'm in the process of migrating a Windows 2000 domain whose old servers ... > due to lots of misconfigurations, hardware problems and a dead Exchange ... > server, so we tought it was better to create a completely new one instead ... > only to get a blue screen after rebooting; I never ran a direct upgrade (I ...
    (microsoft.public.windows.server.general)
  • Re: A difficult migration (2000 -> 2003)
    ... > I'm in the process of migrating a Windows 2000 domain whose old servers ... > due to lots of misconfigurations, hardware problems and a dead Exchange ... > server, so we tought it was better to create a completely new one instead ... > only to get a blue screen after rebooting; I never ran a direct upgrade (I ...
    (microsoft.public.windows.server.active_directory)
  • Re: A difficult migration (2000 -> 2003)
    ... > I'm in the process of migrating a Windows 2000 domain whose old servers ... > due to lots of misconfigurations, hardware problems and a dead Exchange ... > server, so we tought it was better to create a completely new one instead ... > only to get a blue screen after rebooting; I never ran a direct upgrade (I ...
    (microsoft.public.windows.server.migration)
Loading