Re: Trend CSM - upgrade from 2 > 3 - findings thus far
- From: "David Elders" <david_elders@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Nov 2005 19:48:27 -0000
Gonna try uninstalling then reinstalling the whole suite next with a reboot
in the middle...
Cheers,
David
"David Elders" <david_elders@xxxxxxxxxxxxxxxxxx> wrote in message
news:etpd4xJ5FHA.3592@xxxxxxxxxxxxxxxxxxxxxxx
> Yup... and now it won't uninstall [although its in the Add/Remove Programs
> list] and if I try to reinstall it says its already installed!
>
> Think this is gonna be an emergency call first thing in the morning
> [UK]...
>
> Cheers,
>
>
> David
>
>
>
> "Gary Karasik" <gkarasik@xxxxxxx> wrote in message
> news:%23b0V$tJ5FHA.2364@xxxxxxxxxxxxxxxxxxxxxxx
>> Just curious: Did you try uninstalling/reinstalling the client on the
>> server?
>>
>> GaryK
>>
>> "David Elders" <david_elders@xxxxxxxxxxxxxxxxxx> wrote in message
>> news:eDdstrJ5FHA.2040@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi all,
>>>
>>> Thought it worth putting my findings down as it appears not many have
>>> done
>>> so thus far...
>>>
>>> Upgrade installation went like an absolute snap - far less input than
>>> even
>>> the v3 guide had led us to expect. Everything seemed fine at first:
>>>
>>> New Dashboard opened up first time - does indeed look like a massive
>>> improvement on the old, separate consoles and far easier [and quicker]
>>> to
>>> navigate. Everything looks cleaner and more organised in general.
>>>
>>> Then came our [major and so far unfixed] problem...
>>>
>>> As per the previous v2 installation guides [excellent] from sbsfaq.com
>>> we'd
>>> set-up our Server previously with separate logistical groups for
>>> Servers,
>>> Workstations and Laptops [and another for home PCs that would
>>> occasionally
>>> connect remotely]. All the groups were there and all the machines were
>>> correctly noted within their groups. All the settings for each group had
>>> transported across correctly.
>>>
>>> However... our SBS Server [within our defined Servers group] was listed
>>> as
>>> being Offline. We tried a reboot - no joy. Error on reboot that 'at
>>> least
>>> one service... yada yada'. Service was the Officescan NT Listener and
>>> also
>>> the Trend Master Security service. Master service restarted manually
>>> fine.
>>> Officescan NT Listener did not. Bah!
>>>
>>> So, manually removed the Server from the Servers group then manually
>>> uninstalled the Trend Security Client from the SBS Server. Then,
>>> manually
>>> reinstalled. Again, service wouldn't start. Rebooted - same again.
>>>
>>> No rhyme or reason as to why it won't work - no errors in the Event
>>> logs.
>>> Nothing clear on the Trend side. Starting to worry...
>>>
>>> SBS 2003 Premium with SP1 + Exchange 2003 SP2 + Sharepoint SP2
>>> 2 NICs + ISA 2004
>>> 2Gb RAM [only handling 6 LAN clients]
>>>
>>> Will update you with how we get on...
>>>
>>>
>>>
>>> David
>>>
>>>
>>>
>>
>>
>
>
.
- References:
- Trend CSM - upgrade from 2 > 3 - findings thus far
- From: David Elders
- Re: Trend CSM - upgrade from 2 > 3 - findings thus far
- From: Gary Karasik
- Re: Trend CSM - upgrade from 2 > 3 - findings thus far
- From: David Elders
- Trend CSM - upgrade from 2 > 3 - findings thus far
- Prev by Date: Exchange Service Pack 2
- Next by Date: Re: Exchange Service Pack 2
- Previous by thread: Re: Trend CSM - upgrade from 2 > 3 - findings thus far
- Next by thread: Re: Trend CSM - upgrade from 2 > 3 - findings thus far
- Index(es):
Relevant Pages
|
Loading
