Visit www.TCU.edu

Connectivity Requirements

 

 IP Only

No TR Support

Externally Housed

 IP Only

TR Support

Internally Housed

 IP + Domain

TR Support

Internally Housed

 Must abide by the Acceptable Use

(TCU Computing Resource Policy)

 yes  yes  yes

 Disconnect w/ Notification

(should they fall out of compliance)

 yes  yes  yes

 Disconnect w/o Notification

(severe disruption, hack, etc)

 yes  yes  yes

 If disconnected - does TechServ

help them get back to compliance?

 no  yes  yes

 Right to restrict services/ports

(napster, dhcp)

 yes  yes  yes

 Legally licensed server software

(must provide copy of license)

 yes  yes  yes

 Tech Services is local administrator

(or know a local admin user/pass)

 no  yes  yes

 3rd Party Local Admins

(such as some support contractor)

 yes  yes  no
 3rd Pary Remote Access ablility  yes  yes  no

 Patch Level Compliance

(must they meet our patch level)

 yes  yes  yes
 Anti-virus  recommended  recommended  recommended 

 Compliance Timeframe - before

we disconnect them?

 14 days  7 days  7 days
 Prior Notification before connecting  yes  yes  yes 

 HW/SW Warranties - must always

be in-warranty.  Recommend any

new purchase have a min. of 2 yrs.

 no  yes   yes 
 Support/TR benefit section      
 Can use our generator?  no  yes  yes 
 Benefits from locked machine room  no  yes   yes 

 TR responsible for backups?

(don't forget cost of backups)

 no  yes  yes

 Use of Operators (e.g. reboot my

server please, monitor uptime?)

 no  yes  yes
 Support for implementing patches  no  yes  yes
 Support for OS version upgrades.  no  yes  yes

 Physical Access to machine room

without TechServ supervision

 no  no   no 
 
  
What's our main goal of this document?  
 1. Safeguard the availability of our existing network  
 2. Minimize "rogue" servers for a variety of reasons  
 3. Create a document based on these concepts that can be signed by the department allowing us to enforce these items.