S
Stu
Is he doin a crash course with MSE?
We love you Bill ... please come back. All is forgiven
Stu
We love you Bill ... please come back. All is forgiven
Stu
R
Randy Knobloch
Stu said:Is he doin a crash course with MSE?
We love you Bill ... please come back. All is forgiven
Our beloved Bill may be on a much needed vacation, Stu.
S
Stu
OK Randy many thanks for that, I guess he`s earnt it . Trust things are okay
with you and family?
Stu
with you and family?
Stu
R
Randy Knobloch
Stu said:
Actually Bill is around as I have seen posts from him elsewhere.
Things are fine with me, thanks for asking, Stu - most kind of you.
Cheers from the other side of the pond.
R
robinb
like I am going- next week- for the
wholllllllllllllllllllllllllllllllllllllllllllllle week
I cannot wait
robin
wholllllllllllllllllllllllllllllllllllllllllllllle week
I cannot wait
robin
S
Stu
Sounds cool R! Enjoy yer hols lovely lady ...
Stu
Stu
R
robinb
thank you stu
robin
robin
Stu said:
B
Bill Sanderson
I've had my head down--I've been migrating a 30-user SBS 2003 domain to SBS
2008. This is a rather complex process involving moving all data and
settings between two physical servers, since SBS 2008 is 64 bit software.
The migration went fairly smoothly, but I've been trying to get clean
results from various "best practices" wizards, and managed to get both the
SBS wizard and the Exchange wizard to give me clean results by the end of
the day yesterday--so I can relax a bit. There are still a fair number of
nits to pick in the log files, but nothing that impacts significantly on the
users.
This was a lot of work, and in general, the users hardly noticed the
transition, which is the way it is supposed to be.
2008. This is a rather complex process involving moving all data and
settings between two physical servers, since SBS 2008 is 64 bit software.
The migration went fairly smoothly, but I've been trying to get clean
results from various "best practices" wizards, and managed to get both the
SBS wizard and the Exchange wizard to give me clean results by the end of
the day yesterday--so I can relax a bit. There are still a fair number of
nits to pick in the log files, but nothing that impacts significantly on the
users.
This was a lot of work, and in general, the users hardly noticed the
transition, which is the way it is supposed to be.
S
Stu
Little wonder. You `ve been keeping your head down I mean. SBS 2003 to 2008
must represent a gargantuan leap in the world of development not to mention
the people who are expected to transitianolise things. The 32 versus 64 bit
component must, in itself, must have presented something of a problem. A
tribute to your expertise, tenacity and a desire to provide your customer
with the requirement. Great stuff !!
Stu
must represent a gargantuan leap in the world of development not to mention
the people who are expected to transitianolise things. The 32 versus 64 bit
component must, in itself, must have presented something of a problem. A
tribute to your expertise, tenacity and a desire to provide your customer
with the requirement. Great stuff !!
Stu
B
Bill Sanderson
The document you use to do the migration is some 200 pages long. There are
wizards, but sometimes what looks like a simple paragraph requires hours of
work. The amazing thing is that you do this between two different physical
servers--and both remain fully functional though most of the migration--and
it really is near-seamless from the viewpoint of the users--who notice very
little change.
There does come a crunch point where, for example, Offline Files users must
have their settings changed--something I believe was not in that 200 page
document. Lots of little details to deal with. Because SBS is normally
limited to a single DC to the domain, there's a special exception in the
installation process that allows 3 weeks from start to completion before the
old server starts rebooting once an hour. I needed most of that time..
We have a fairly complex setup for an SBS install--30 users, an AIX5 unix
server and a Linux based phone system that has phones that work over TCP/IP
and can be used in the office or across the Internet.
For those who enjoy reading sagas, I'll recount my adventure of yesterday,
which confirms my rank amateur status as a network admin and security minded
person:
An administrator handed me his sons laptop which had been exhibiting
symptoms of a failing hard disk. Indeed, at first boot attempt, the bios
did not recognize the existence of the drive. However, on second attempt,
it started just fine, so my first impulse was to do a full backup to a LAN
based Windows Home Server machine as soon as possible.
During the backup I became aware (via about a dozen randomly named
executables in TEMP) of the the machine—that it was infected.
I installed and updated definitions for Microsoft Security Essentials, which
commenced to clean up the mess—the major piece of which seems to have been
win32\Sality.AM.
In the mean time, however, the critter had been pumping out spam as fast as
the gigabyte LAN and (much slower) DSL NAT connection allowed, and we were
blacklisted on the CBL. It took me nearly a day to understand what had
happened, ensure that the machine was clean, and delist us.
At least I've now got the full attention of senior management with regard to
security risks. They are ready to ban connection of machines from offsite,
but I'm exploring several ways to mitigate this issue with going to that
length.
wizards, but sometimes what looks like a simple paragraph requires hours of
work. The amazing thing is that you do this between two different physical
servers--and both remain fully functional though most of the migration--and
it really is near-seamless from the viewpoint of the users--who notice very
little change.
There does come a crunch point where, for example, Offline Files users must
have their settings changed--something I believe was not in that 200 page
document. Lots of little details to deal with. Because SBS is normally
limited to a single DC to the domain, there's a special exception in the
installation process that allows 3 weeks from start to completion before the
old server starts rebooting once an hour. I needed most of that time..
We have a fairly complex setup for an SBS install--30 users, an AIX5 unix
server and a Linux based phone system that has phones that work over TCP/IP
and can be used in the office or across the Internet.
For those who enjoy reading sagas, I'll recount my adventure of yesterday,
which confirms my rank amateur status as a network admin and security minded
person:
An administrator handed me his sons laptop which had been exhibiting
symptoms of a failing hard disk. Indeed, at first boot attempt, the bios
did not recognize the existence of the drive. However, on second attempt,
it started just fine, so my first impulse was to do a full backup to a LAN
based Windows Home Server machine as soon as possible.
During the backup I became aware (via about a dozen randomly named
executables in TEMP) of the the machine—that it was infected.
I installed and updated definitions for Microsoft Security Essentials, which
commenced to clean up the mess—the major piece of which seems to have been
win32\Sality.AM.
In the mean time, however, the critter had been pumping out spam as fast as
the gigabyte LAN and (much slower) DSL NAT connection allowed, and we were
blacklisted on the CBL. It took me nearly a day to understand what had
happened, ensure that the machine was clean, and delist us.
At least I've now got the full attention of senior management with regard to
security risks. They are ready to ban connection of machines from offsite,
but I'm exploring several ways to mitigate this issue with going to that
length.
S
Stu
LOL! Nice job Bill. I shouldn`t laugh really but the failing HD and off site
notebook story sounds familiar. I can only hope senior management have been
wise enough to recognise a good recovery man when they see one. As my dear
`ol pappy once put it. Its not so much the mess you may sometimes get
yourself into son. Its the ability, you may demonstrate, to extracate
yourself from it. That`s putting it politely. There lies the essence of
things and one which I omitted to include in my previous post - all this is
done seamlessly as you say! I`m not sure how I`d feel about that without some
sort of `pat on the back`. On the one hand, it is one helluva an achievement
but on the other? There are few who can comprehend what has really been
involved on the user front. I guess professional pride and personal
achievement in the knowledge of a job `well done` is the order of the day -
just doin`me jo. All in a day`s work?
Stu
notebook story sounds familiar. I can only hope senior management have been
wise enough to recognise a good recovery man when they see one. As my dear
`ol pappy once put it. Its not so much the mess you may sometimes get
yourself into son. Its the ability, you may demonstrate, to extracate
yourself from it. That`s putting it politely. There lies the essence of
things and one which I omitted to include in my previous post - all this is
done seamlessly as you say! I`m not sure how I`d feel about that without some
sort of `pat on the back`. On the one hand, it is one helluva an achievement
but on the other? There are few who can comprehend what has really been
involved on the user front. I guess professional pride and personal
achievement in the knowledge of a job `well done` is the order of the day -
just doin`me jo. All in a day`s work?
Stu