Insatlling a new network

[GrumbleDook]

Scheduling downtime is not a bad thing ... even if you don't always use it.

 

It can be used for any number of helpful things such as part of your normal yearly schedule.

 

Patch management can require restarts.

Migration of user data can require you to say that specified users cannot use certain services during specified times.

Migration of services (eg printers) may mean that you want people off the system to save them getting confused or upset when things are offline rather than it being a requirement.

Upgrading certain software (eg mail server) will require downtime of that service.

And then we get onto the testing of disaster recovery policies.

 

Downtime does not just refer to taking everything offline, but also to just key sections.

 

We can take things of piecemeal if needed, but then you get the constant interuptions about when will it *all* be back on line, etc.

 

Because we have 24 hours access for staff via Remote Access (terminal servers atm, but soon to be available to all users via Sun's Secure Global Desktop) then we cannot just do 45 mins after staff have left ... everything we do has to be scheduled and published to staff and students.

 

I notice that when you say install 2003 you fail to mention 'patch 2003' ... even if you have all the patches to hand it still takes time.

 

But this is just the way our school works ... if yours works differently and is fine for you, then fine.

[Joedetic]

"But this is just the way our school works ... if yours works differently and is fine for you, then fine."

 

This is a view i have on most things (Distro wars especially!) Sure x-solution might work for group-A but it might not necessarily work for group-B. Group-A should always accept that whilst it's group-B might like to know about x-solution, they have every right to stay with y-solution. If you get my meaning in all of that jumbled nonsense. Basically only do something if it suits your way of working/computing.

 

With regards to downtime. You are always going to get downtime. It's unavoidable to keep an up -to-date and secure, stable infrastructure right from the physical network media up to applications and patches etc.

[Guest Guest]

I notice that when you say install 2003 you fail to mention 'patch 2003' ... even if you have all the patches to hand it still takes time.

 

Ahh fair enough. Id forgot about that as our last install was 2003 R2 which is obviously more upto date. I would normally use either WSUS or incorporate as many updates as i can into the RIS/CD image, but yeah i agree i was probably abit optomistic in my time allocation in light of updates.

[john]

Adding a new printer is a breeze for us.

 

• Set static IP either using front panel buttons or web interface
  
• Install printer on server by creating new TCP/IP port
  
• Name printer
  
• Share printer
  
• Allocate to workstations/rooms via RM Management Console
  

 

And thats exactly how I do it on Server 2003 R2 Craig

[webman]

@john: What, you even use the RM Management Console to easy allocate the printer to workstations? :shock: