Gather information on the devices to be moved and develop your plan.
Make a list of the devices to be moved. You may either use our
checklist (link coming soon) or create one of your own. This list is for
your records and does not need to be sent to anyone.
Verify that applications on the workstations/servers being moved are
on the tested
applications list.
Inventory applications.
Confirm each application has been tested for the MSN.
Test any applications not already comfirmed as tested.
Send email to secnet@virginia.edu advising of any test results for
applications not on the list.
Plan the sequence for moving your devices.
If you are moving a server and the workstations that access it, move
the workstations first.
Look at the set of workstations to be moved and group them in
reasonable subsets. When unforeseen issues/problems arise,experience has
shown that subsets of 12 or less work best.
Consider the relationships and dependencies between your workstations
and servers before determining the makeup of a group.
If you are movng a server but not all the users who need to access it,
then users who stay on the standard University network will have to obtain a
MSN VPN.
Resolve communictions issues.
Determine any static IP address that will be changed (servers,
printers, etc.) These will require special coordination with Hostmaster.
If you have a server that is not moving to the MSN and this
server needs to communicate with one that is, then the communication must
be initiated by the server on the MSN.
Notify people who are not moving but access data or applications on
servers or workstations being moved that they will need to obtain a
MSN VPN.
Advise people who will require a MSN VPN that they can not
concurrently use other services that require a VPN connections, i.e.
Oracle
Determine how Broadcast Services will be handled.
Broadcast-based services between the MSN and the standard
University network in your building will require special consideration.
Even though the two networks are in the same building, they do not
directly communicate. This includes services like browsing via network
neighboorhood to locate computers on another network. In this case,
configuring WINS on your workstation may provide a workaround. You can use
ITC's WINS server: 128.143.3.199 and 128.143.22.189 if you do not run
WINS.
LMHOST files may be used as an alternative to WINS. These will have to
be maintained individually on each workstation.
Verify that each device to be moved is connected to one jack and it
is the only device on the jack (no hubs/switches).
Inform ITC's Network Systems and your departmental staff about the
upcoming move.
Send email to networks@virginia.edu advising them of your department's
intention to move workstations and/or servers to the MSN. Include
a preliminary estimate of the number of devices you intend to move.
Send email to departmental staff advising them of the impending move.
Including the proposed date, the expected downtime, and noting any
workstation changes will probably save you some extra emails.
Steps to take if you are moving Windows Active Directory.
Notify Hostmaster at least a week prior to making the request that you
will be requesting IP addresses for the MSN and that this will
involve relocating an Active Directory. You will receive an email
acknowledging your request and giving you a date for the move.
Plan your move for the end of the work day, since there will be a day
of downtime due to DNS servers scheduled rebooting sequences. Remember to
notify users when you do this, because they will not be able to access
resources until the following day.
