Server FAQs

You may request a new server using the Hosted Service Request Form.

• Microsoft Windows 2019
• Microsoft Windows 2022
• Red Hat Enterprise Linux 8

If you have an emergency please contact the IT Assistance Center.

For general inquiries or requests involving hosted services, you may submit a Server Support Request.

The server names themselves are determined by the Systems Administration Team (with your input), but you are permitted to request an alias (DNS CNAME) to have a friendlier name for your end-users.

Example Server Name: itacweb1.matrix.txstate.edu

Example Alias: frontdesk.itac.txstate.edu

Naming conventions still apply when requesting an alias for a fourth level domain or higher (see UPPS 04.04.08).

1. You can request VPN access via infosecurity@txstate.edu if your system needs to be accessible through VPN.
2. If you need access off-campus and it can't go through VPN
   • Request a vulnerability scan
   • Request a firewall exemption
   • Request your DNS record (service.department.txstate,edu) to be published externally.
     • If you are requesting a third level (X.txstate.edu) please submit a Third Level URL Request.
       • NOTE: These are heavily restricted and governed via UPPS.04.01.08.
     • Server Support Request

Applications/software must be reviewed by the Information Security Office. This can be initiated by submitting a Service Evaluation Request.

Numerous options exist and should be established in your data security plan from Information Security Office.

At this time, only our Red Hat Enterprise Linux servers are configured to allow for certificate-based authentication.

• We utilize Duo Multi-Factor Authentication.
• If you would like to add DUO to your SSH or RDP, please submit a Server Support Request.
• If you would like to add DUO to your application and it supports it, you may request an integration key from infosecurity@txstate.edu.

• File and Data Storage and Sharing
• OneDrive, Department Share, Teams for data storage and sharing
• SFTP Service
  • Secure file transfer from other systems
• Secure File Transfer
  • Web front-end for receiving files to users or groups of users
• Gato Content Management System
  • Hosting academic and administrative department websites

Using the short name/NetBIOS name (server instead of server.dept.txstate.edu) is not recommended nor supported. The DNS name of Fully Qualified Domain Name should be used in all cases.

You may contact ITAC with your request of specifications and budget. 

We may only house systems that were purchased or coordinated through Technology Resources and meet various requirements such as vendor, warranty, etc.

• Teams/Zoom where the application admin shares their screen
• Guest account with VPN access
  • NetID request
  • TXST sponsor put in ticket to itac@txstate.edu

You may review the shared responsibility model to list the separation of duties between application and systems administration. The Systems Administration team will provide the server, network, backups, OS updates. Systems Administration can also be of assistance in connecting to other University-managed services. Any assistance with installation/configuration/upgrades of your application should be directed to your software vendor or a consultant.

Microsoft Windows

A role (Active Directory Group) is made available in the Online Toolkit. The name will traditionally follow the format of RDP-<servername>-Admins. For example, if your server name is itacapp1, the group would be RDP-itacapp1-Admins.

Any changes to this group should come from the role manager of the group. If you do not know who that is, or one is not assigned, a ticket to ITAC requesting the manager or addition of a manager can be sent.

Red Hat Enterprise Linux

There are two primary ways for controlling access to a RHEL server.

1. A role (Active Directory Group) is made available in the Online Toolkit. The name will traditionally follow the format of RDP-<servername>-Admins.
   
   EXAMPLE: If your server name is itacapp1, the group would be RDP-itacapp1-Admins.
    
2. A configuration management tool (Puppet) can push the configuration of administrators to a server or a group of servers. You will normally see a designated group of administrators in the same team or department have the exact same access to all that team/department's servers.
   
   EXAMPLE: ITAC may have 3 personnel that manage ITAC Linux systems. Those same 3 administrators would be part of the same group that is pushed to all ITAC Linux Systems.

NOTE: Changes to your server may be requested via the Server Support Request. You can also use this request if you have access to a server and need to be removed as an admin.

As an administrator, you may install and configure software and are responsible for the operation/maintenance of your software. You may reference the shared responsibility model for more detail. 

Administrative permissions for a server inherently entail responsibility for the operation of that server and adhering to all university policies. Texas State adheres to the principle of least privilege. Application administrators are responsible for auditing access to their server and applications via means such as Role Management or application-specific records. Access that is no longer necessary for the administration of the system must be removed.

Requests for general server changes (firewall, access, shares, etc.) can be made via the Server Support Request.

Requests for decommissioning may be made via the Server Support Request.

TXST University servers may be housed in one of our data centers on the San Marcos campus. Servers provisioned via the Hosted Service Request will be virtual.

We do not have any SLA for uptime.

At this time, there is usually no cost for running a server in the data center. As this is a shared university resource, if compute (CPU/Memory) or storage requirements are high, there will be additional discussion needed.

TXST Faculty and Staff.

https://doit.txstate.edu/rc/leap.html