Page tree
Skip to end of metadata
Go to start of metadata

 

On-boarding

When a new user starts, HHR works with the Admin group at HUIT

Fill out the Service Now form by going to harvard.service-now.com/selfservice 

  • Log in with Harvard Key
  • Select HUIT Administration block
  • Click on Onboarding Request form. 
  • Enter required fields.
    • The should have access to \\sox1.university.harvard.edu\uis-dls\Projects\
      • Techs will also need access to \\sox1.university.harvard.edu\Uis-Migr-A
      • The two default security group access needed - UIS-NSS-Login-Script-dgs and uis-dls-dgs
    • Request a g.harvard.edu account
    • Request access to the dlsadmin VPN tunnel
    • Access to 1033 Mass Ave. Techs will also need access to 65R
      • Coops will need access to the above plus, 8 Story St, Vanserg (all as of 6:30AM)

This Request will generate several tickets

Once their HUID is created, they can get their ID at the CSC in SCC

They should claim their Harvard key then.

Additional  ServiceNow tickets:

ESM – LANDesk for imaging

ESM – Casper for access to console and for imaging (may require additional ticket)

Managers and Project coordinators need access to MIDAS

  • Fill out the Service Now form by going to harvard.service-now.com/selfservice 
  • Log in with Harvard Key
  • Select Identity & Access block
  • Click on Request for Midas Access
  • Business Reason: Need to see department and role of Harvard faculty and staff in order to determine program eligibility and location during desktop refresh cycles.

Managers and Project coordinators need access to

  • Survey Tool Need info
  • AMOS, the Leasing company’s asset management system

For Coops and Deployment Techs – request "a" account

  • Fill out the Service Now form by going to harvard.service-now.com/selfservice 
  • Log in with Harvard Key
  • Select Identity & Access block
  • Click on Request for Privileged AD Access
  • Business Reason: Technician needs access to generate machine names, add machines to the *both* the University and FAS domains. Also perform administrative tasks on desktop and laptop computers. Approved by Manager Bruce Patterson

Email Peg Davis to add the new user to the huitsupportservices@mailman.fas.harvard.edu

 

Once they have their "a" account

  • AAM - Submit request for DNA access
  • AAM - Submit request FAS Domain Joiners access.
  • ESM - Submit request for LAPS access using "a" account
  • ESM – Request for Crash Plan console
  • ESM – Request for Parity console

Share the following Google Calendars

FAS Refresh – Read and write

CA Rollouts – Read and write

Field Support Project team – read access

 

Send emails to get access to additional building spaces. Send name and HUID. It is a good idea to remove anyone that has left at the same time

 

 

 

 

Hire Coop

Harvard Funding Approval Process

Wentworth Posting process

Create an account in the Wentworth site https://wit-csm.symplicity.com

Under Jobs create a posting. Select the current posting to replicate the last one. Continue through the form, filling it out. FYI this is the description we have been using for the last few years.

Description:

Work with Harvard Computer Deployment Team
We are looking for an individual with an excellent attitude and work ethic to work with a smart and talented team of Harvard technicians and program managers. This individual will assist with the deployment of Windows and Apple computers.

This person will juggle various tasks, prioritize them, communicate the status of projects, and come to anticipate the needs of the team. Lots of opportunities to take initiative.
Responsibilities include:
Delivery of equipment across campus (will be driving our van around campus in Cambridge and Allston)
Track inventory of computers in various locations, maintaining spreadsheets and communicating with the team
Image computers using LANDesk and Casper
Install software, run updates, etc.

Wipe hard drives
Manage storeroom, keeping it organized and take weekly inventories

Qualifications

Driver's License in good standing
Able to lift boxes of computer equipment

 

Save the Job, make sure there are no red sections (missed or incorrectly formatted information). Then submit for approval. This takes a days.

You will receive emails with resumes and cover letters. Track these as they come in. Keep a spreadsheet with Candidates names, pros and cons based on resume and then keep notes on who you want to contact, communications and results.  Usually you do phone interviews with several and have 2 or 3 do in person interviews.

Once you select the candidate, make sure you send the offer with their expected hours, hourly rate, and start date. They need to respond to the email to accept the offer. Be sure to let them know what the dress code is.

Fill out the HR form HUIT Temp Registration Form:

Available on the HUIT Intranet under POLICIES, FORMS & RESOURCES / Manager Resources for Hiring & Onboarding / Forms and Documents tab https://intranet.huit.harvard.edu/files/huit-intranet/files/huit_tempregform_2015_0.pdf

Start the on-boarding process as soon as possible. New accounts can take over a week.

Come up with a plan to train the coop. See if previous coop can overlap. It usually takes 5-7 mornings before they are able to do the morning delivery on their own.

Review Coop manual to see if needs to be updated.

 

Planning Rollouts

Master Rollout Status sheets

For long term planning use the OneDrive  Rollout Status sheet.

The current fiscal year, and the next fiscal year should be filled out. Use Lease information from AMOS

Use other department inventories to file out CA purchase deployment numbers

Use the FAS Refresh inventory sheet in Google to calculate the quarterly numbers

Contact customer

10 to 12 weeks before the beginning to the quarter reach-out to customer. In this communication, let them know how many computers we have estimated that need to be refreshed and the time frame. If this department has a special image, a testing Also in this email is their inventory and instructions on how to make selections.

  • There is a link a spreadsheet with their current inventory.
  • Computers up for refresh in the coming quarter are identified
  • There is also a link to current the computer standards.
  • There are instructions on how to make selections.
  • There is a deadline for when they need to make their selections.

Quarterly planning

The deployment manager the deployment coordinator meet 6 months prior to the quarter to plan the schedule. Using the Master Rollout Status sheet, they plan the dates for each department rollouts. Taking into consideration:

  • Customer responsiveness in making selections
  • Any special images that need to be tested
  • Expected delivery date of leased equipment
  • Lease return date
  • Holidays
  • Vacation days of technicians
  • Availability of Field Technicians to assist

Hardware standards

Endpoint Management Systems is responsible for selecting and maintaining the computer hardware standards. But the deployment managers and involved in the decision process.

Most Dell laptops are updated once a year, in the spring and desktops models are updated every 18 months to two years.

The life cycle of an Apple computer is more difficult to predict. Often new models have long lead times.

 

Special images

Ordering

Leases

Logistics – space and shipping

Purchases  billing codes and HCOM

The customer review this inventory. Machines that are due for refresh are highlighted. For each machine, they choose a new machine to replace it with and check the keyboard, mouse, dock and monitor boxes if applicable.

This sheet is used throughout the deployment process so it is important to keep it up to date and accurate.

Receive and prepare equipment

Receipt of FAS Refresh or large rollout inventory.

All ordered equipment is received by Katie McNaught and Joe Roberts. These steps refer to equipment for large rollouts or for FAS Refresh equipment.

  • They update the order sheet in OneDrive, to note what is received.
  • Mark as received in HCOM if they were purchase
  • For each computer, they scan the serial number and enter the department, user name (if they know it, model info, and order number into the appropriate inventory sheet. There are separate inventories for CA and FAS.
  • They label the equipment that notes what it is and what department it is for or the lease number. If they know the user name from the request that will also be on the label.
  • FAS Refresh machines are labeled with the quarter they were received. i.e. FY17Q3
  • They bring the equipment to the storeroom. They group department machines together, CA in the first part to the storeroom and FAS in the back.

Prepare

Coops are responsible for most of the imaging. But the techs do jump in and help out if the coop is too busy.

  • For large rollouts, computers are imaged shortly have they are received. But the coops do use the Google scheduling calendar to prioritize what needs to be imaged.
  • For FAS, machines are imaged several days before deployments. The techs use the Google scheduling calendar to determine what needs to be imaged.
  • Machines are imaged, drivers updated, security updates are applied and then they are added to the domain.
  • Machines are also labeled.
    • Ptouch labels for Lease machines are attached
    • FAS Refresh machines are labeled with their return quarter
    • Harvard inventory labels are attached (Htags for CA, gold tags for FAS)
  • Refer to Coop manual for more details about imaging and prep

Label with User Name

For FAS Refresh deployments, when it is scheduled, a computer from stock is selected

  • The user’s name is written on the box
  • In the FAS Computer inventory sheet, the status is changed to In Stock- Reserved and the user’s name is entered

 

For CA rollout machines

  • The coordinator works from the rollout whole inventory sheet
  • For each scheduled machine, locate a machine that is from the correct lease and is the correct model
  • The user’s name is written on the box.
  • The serial number is scanned from the box, into the rollout whole inventory sheet

Delivering computers to Field to deploy

Often Field Techncians deploy new computers.

Make sure there is a ticket, either one from the original order

Scheduling

Site logistics

              Storage, securel locations

FAS Refresh

CA customer schedules

CA we schedule

 

Techs responsibilities

In addition to the daily rollouts, technicians are responsible for other administrative but deployment related daily tasks

Plan for up-coming deployments

Claim deployments

All deployments are in the Google calendars. There is a one calendar for FAS and one for CA, but you can see both at the same time. Techs should go to https://www.google.com/calendar/hosted/g.harvard.edu and make sure both CA Rollout Calendar and FAS Refresh calendars are selected under My calendars.

Techs should review the schedule for the current day and the next day to see if there are any changes. Make sure they still have two deployments scheduled for each day. 

Next, they should look two days ahead claim their deployments. Often the deployments will be notes with a number in the beginning of the title. That is method the scheduler denotes which deployments should be paired because they are in the same area on campus. Be sure to select the two with the same number. Put your initials in the beginning of the title between brackets – []

Sending reach-out emails to customers

Techs are responsible for sending reach-out emails to customers two days prior to their scheduled deployment.  Be sure to review the calendar entry, there might be another contact person. Use the email template in Appendix A

Equipment

For next day’s deployments

They have the new equipment. Techs are responsible for checking to make sure they know where the equipment (computer and any peripherals) for the next day is and that it is imaged and ready to go. If they are working at the customers location as part of an on-site deployment. They need to check the morning before to make sure their equipment is on site. If not, they should contact their manager and the project coordinator so there is time to deliver the equipment

If they are working in our office, they need to check the storeroom to make sure it is ready to go.

If they plan to work at an alternate location, they are responsible for contacting the coop to make sure the equipment (computer and peripherals) gets delivered the next morning to the closest regular delivery location.

Also, they need to confirm that there is a deployment loaner available if required. They should know if they need a loaner from their communications with the client.

Return of Old Equipment

Techs are responsible

  • Removing DDPE from old machine
  • Labeling it with the Old Computer label
  • Making sure it is in a locked secure location
  • There is a plan to get it back to 1033 Mass Ave
    • If they are working on-site in a designated rollout room they should be organized and grouped together so coop knows where to collect them from
    • If they are working at a HUIT location, but not a designated delivery location, they need to bring it to a designated deliver location and make sure coop knows to pick them up the next morning
    • If they are in designated delivery location, make sure coop knows to pick them up the next morning

Keep office and work area cleaned up and organized

Planning Rollouts

For long term planning use the Rollout Status sheet. This should have the current fiscal year, and the next fiscal year filled out.

Contact customer

10 to 12 weeks before the beginning to the quarter reach-out to customer. In this communication, let them know how many computers we have estimated that need to be refreshed and the time frame. Include a link to their inventory and a link to the computer standards. Include a deadline for when they need to make their selections

The customer review this inventory. Machines that are due for refresh are highlighted. For each machine, they choose a new machine to replace it with and check the keyboard, mouse, dock and monitor boxes if applicable.

This sheet is used throughout the deployment process so it is important to keep it up to date and accurate.

Deployment Process

PreDeployment:

As noted in the Technicians Responsiblities section the tech should have the following done before the day of deployment:

  • Communicated with the customer to confirm location and time of pickup and any additional software. This was done with the Reach-out email (see Appendix 1) by the coop, but the tech should confirm the day before that the machines has been imaged and is on site.
  • If the customer needs a deployment loaner
  • Confirmed that the new equipment is imaged and on site    

Need to update to iterate what applications in the appt

Loaners

KMM what template are folks using [CA1]  

Deployment:

Pick up old computer from customer

The tech meets the customer at their location in order to pick up the old computer from the user and bring it to the their work space. Using the Deployment sheet, they fill it is as they go through the pickup process with the customer.  Please note that customers are sometimes in a rush and may not have time to go through all these steps. The following is priortized to get the most important information up front.

  • If moving from a Windows to a Mac machine or visa versa, bring the new computer to the meeting so that the user can create a Windows profile/ Mac User account to which you can migrate the data.
  • Check the serial number on the old machine and confirm it agrees to the one in the appointment.
  • Make sure the huitadmin account is on the machine
  • Assess how much of the current drive is in use and compare to new drive. You may need to talk to the customer about moving files to the cloud.
  • Review applications with customer
    • Make sure they have licenses to any that are required
    • Ask about any you are unsure of
    • Confirm drive mappings and any other settings
    • Check with the user to ask it they have any concerns
    • Discuss the time you projected time of delivery of the new computer. Be sure to explain that unexpect issues can arise and that this is an educated guest.
    • Collect the old travel charger
    • Note if there is a static IP and record it
    • Document the wired and wireless Ethernet addresses

Migrate data and install applications

Tech returns to their work space with the old computer to migrate the date from the old computer to the new computer. Use the Deployment sheet and fill it out as you go through the migration process.

 

Windows

Back up customer data - Following the USMT documentation, back up the customer’s data from the old machine

Prepare new machine –

  1. Confirm the new machine has an appropriate machine name and is added to the domain
    1. Make sure the prefix of the machine name machines the department
    2. For CA machine names use the Dyonsis tool to create the name
    3. If this a FAS machine, use the DJU to create the machine name. IMPORTANT: check Active Directory to make sure that the machine name is not already used. If it is increase the number at the end.
  2. Confirm that the BIOS and drivers were updated during prep. It is often noted on the box.
  3. Add UIS-DLS-DGS to admin group
  4. Install all additional applications
    1. * If installing Hyperion make sure you do this as soon as possible in the process. This application can blue screen a machine. That means the machine has to be reimaged.
    2. Most software and licenses are in \\sox1.university.harvard.edu\uis-dls\software
    3. Use https://ninite.com/ for free applications
    4. FAS machines have access to the full Adobe Creative Cloud suite via the LANDesk portal

Restore data to new computer, following USMT documentation.

 

Finish preparing new computer

  1. Login to the new computer with the local huitadmin account
    1. If migrating form W7 to W10, then delete the printers and reinstall them with the correct W10 driver.
    2. Enable all Macros on Word and Excel
    3. If the machine requires encryption (all laptops and some desktops) enable BitLocker managed by DDPE
    4. If the machine returning to FAS building then check AutoReg for old IP. If it is reserved, move the reservation to the new machine. If not, create new AutoReg record for wired connection of new machine
    5. If this is a CA department or FAS Security-in-a-Box department, install Parity Bit 9
    6. Run a LANDesk Security Scan and an Inventory Scan
    7. Review the Deployment sheet and confirm that everything is done.

 

Deliver the new computer to the customer

The new equipment and About Your New Computer cards are delivered to the user.  All the computer eqiupment detailed in the calendar entry are set up for the user. Make sure all Dell laptop users get their travel power adapter.

  1. If this is a laptop assist the customer with registering the wireless connection to Harvard Secure through getonline.harvard.edu
  2. Adopt CrashPlan account from old machine and have users login for all FAS users & any CA users with account.
    1. Note: All FAS machines should have CrashPlan installed
  3. Launch Microsoft Outlook, confirm all mailboxes and additional profiles are functional.               
    1. Verify all PST files are re-mounted.
  4. Enable or Install Accellion Outlook plugin for CA & FAS Security-in-a-Box users.
  5. Have customer confirm all needed printers are installed, re-set default printer if needed.
  6. Have customer test any necessary web apps/software/applications, confirm they’re functional and licensed.
  7. If Customer has Adobe CC license have customer install and test, confirm they’re functional and licensed.
  8. Have customer verify all network/shared drivers are re-mapped and functional.
  9. Confirm VPN preferences were migrated to new computer
  10. Fix/remove any broken shortcuts on the desktop, pinned to taskbar/dock, or pinned to Start Menu
  11. The tech leaves their business card

 

We  make ever effort we can to make sure the user is there at drop of, but if the user is not there:

  1. Leave About Your New Computer cards
  2. Technician’s business card
  3. If it is a laptop, information about how to setup Harvard Secure network
  4. If the user need CrashPlan, submit a ticket for CrashPlan adoption

 

Macintosh

Migrate Data from old machine to new machine

  1. Set old machine in target mode. 
  2. Connect the old machine to the new machine using Thunderbolt/Firewire. 
  3. Log in as HUITadmin on the new machine.  
  4. Navigate to the new computer's User folder.
  5. Access the old machine as an external drive and navigate to the Users folder.  
  6. Drag the user's Home folder from the old machine to the new machine's User folder. 
  7. Wait for the transfer to complete. 
  8. After the folder has been transferred to the new machine, create a new user on the new machine under the user's name from the old machine. Set the passwork to the standard one. 
  9. Use the same username that’s labeled on the Home folder that you transferred from the old machine in the "Account Name" section during the user creation.  
  10. Upon creating the account, a pop up will ask you if you want to inherit the existing folder that was found. Click "Use this folder". 
  11. Restart the old machine and login with HUITadmin.
  12. Copy ppd and printer.conf from the /est/cups folder on the old machine. Place those into the same folder on the new machine. 

Finish preparing new computer

  1. Confirm the machine has an appropriate machine name. Macs do not get added to the domain. (this policy is as of Dec 2016 because of the Sierra operating system)
    1. Make sure the prefix of the machine name machines the department
    2. If this a FAS machine, use the DJU to create the machine name. IMPORTANT: check Active Directory to make sure that the machine name is not already used. If it is increase the number at the end.
  2. Install all additional applications
    1. Most software and licenses are in \\sox1.university.harvard.edu\uis-dls\software
    2. FAS machines have access to the full Adobe Creative Cloud suite via the LANDesk portal
  3. Login as the user on the new machine. 
  4. If a laptop, Enable Filevault on the new machine. Make sure that HUITadmin is enabled as a user to decrypt the machine. 
  5. If the machine returning to FAS building then check AutoReg for old IP. If it is reserved, move the reservation to the new machine. If not, create new AutoReg record for wired connection of new machine. 
  6. Review the Deployment sheet and confirm that everything is done. 

 

Deliver the new computer to the customer

The new equipment and About Your New Computer cards are delivered to the user.  All the computer eqiupment in the calendar entry are set up for the user.  

  1. Have the customer login and make sure they change the password
  2. If this is a laptop assist the customer with registering the wireless connection to Harvard Secure through getonline.harvard.edu
  3. Adopt Crash Plan account from old machine and have users login for all FAS users & any CA users with account.
    1. Note: All FAS machines should have CrashPlan installed
  4. Launch Microsoft Outlook, confirm all mailboxes and additional profiles are functional.               
    1. Verify all PST files are re-mounted.
  5. Enable or Install Accellion Outlook plugin for CA & FAS Security-in-a-Box users.
  6. Have customer confirm all needed printers are installed, re-set default printer if needed.
  7. Have customer test any necessary web apps/software/applications, confirm they’re functional and licensed.
  8. If Customer has Adobe CC license have customer install and test, confirm they’re functional and licensed.
  9. Have customer verify all network/shared drivers are accessible and functional.
  10. Fix/remove any broken shortcuts on the desktop, pinned to the dock
  11. The tech leaves their business card

 

We  make ever effort we can to make sure the user is there at drop of, but if the user is not there:

  1. Leave About Your New Computer cards
  2. Technician’s business card
  3. How to log in and change the password
  4. If it is a laptop, information about how to setup Harvard Secure network
  5. If the user need CrashPlan, submit a ticket for CrashPlan adoption

Processing Old Equipment

  1. If DDPE is on old equipment PBA is disabled and DDPE is uninstalled
  2. The old equipment is labeled with the Old Equipment label .
    1. Includes the Customer Name, Department, date of Refresh, wipe date, tech name, lease or purchase,  PBA is Disabled and the Serial Number. 
    2. The calendar entry will tell you whether it is leased or purchased.
  3. Desktops - The desktop label is taped to the front facing side.
  4. Laptops  - the travel charger goes in the box the new computer came in. The laptop label on side of the box so it can be read when they are stacked
  5. The old equipment is kept in a secure location – either on site if working from customer location or in one of the HUIT cages – 1033 Mass Ave, Vanserg or 65 R Mt Auburn
  6. Boxes
    1. LAPTOPS - Old laptops are supposed to go in the new laptop box – both leased and purchased. But if this is for a new user or if their old machine was a desktop, please return the box to back corner of the storeroom. We need them all.
    2. iMacs -  also all old iMacs should be boxed in the new iMac box. Even if you have to remove the packing material, please put in the box for shipping.
    3. We are shipping all old equipment – Lease AND Purchase

 

Surveys

Surveys are sent once a week for

Returns

Managing Storeroom

 

Managing Loaners

Managing Deployment Loaners

Deployment loaners are available for the day of deployment. They have deep Freeze install so that upon reboot they are back to their original state and no data is installed on them.

The list of the loaners is in https://docs.google.com/spreadsheets/d/1uvXlnYeP355WUYbiugA-KEIGjoQHUDPaTzuRqDLweQA/edit#gid=0 . The location is updated when they are brought to an on-site deployment location and when they are returned.

As the loaners are used, the tech signs them out, using the Log tab in https://docs.google.com/spreadsheets/d/1uvXlnYeP355WUYbiugA-KEIGjoQHUDPaTzuRqDLweQA/edit#gid=0 . When they are returned, they are signed in.

On a quarterly basis or so, the deployment loaners are reimaged and prepared as follows:

Windows Deployment Loaners Maintenance

  1. Make sure you have adapters for all of them (must be travel adapters)
  2. Image with the latest CA image, update drivers and run LANDesk security scan
  3. *Before* adding it to the domain, create a local account “loanuser” with no password
  4. Use the naming convention HUIT-DplyLoan01 – using the number on the label
  5. Add to the FAS domain (Can still log on to CA domain with university\adid). The FAS domain is better because we can use informative machine names
  6. Test logging in with both FAS_domain and University credential
  7. Log in with loanuser
  8. Install DeepFreeze O:\Software\DeepFreeze\Deep Freeze\1033\1033.exe
  9. Login as loanuser and confirm the machine is Frozen
  10. Update the Deployment loaner sheet (tab Deployment Laptop Loaners) with the  current location and date it was reimaged https://docs.google.com/spreadsheets/d/1uvXlnYeP355WUYbiugA-KEIGjoQHUDPaTzuRqDLweQA/edit#gid=0  
  11. Put them in the rack in M20

 

Macintosh Deployment Loaners Maintenance

  1. Image with the latest CA image, run updates
  2. Create a local account “loanuser” with no password
  3. Use the naming convention HUIT-DplyLoan08– using the number on the label
  4. Install DeepFreeze O:\Software\DeepFreeze\Deep Freeze\Loaner\Loaner\Loaners.pkg
  5. Login as loanuser and confirm the machine is Frozen
  6. Update the Deployment loaner sheet (tab Deployment Laptop Loaners) with the  current location and date it was reimaged https://docs.google.com/spreadsheets/d/1uvXlnYeP355WUYbiugA-KEIGjoQHUDPaTzuRqDLweQA/edit#gid=0  
  7. Put them in the rack in M20

Administrative policies

Hours

  • Technicians hours are 8AM to 4PM with an hour for lunch
  • Lunchtime is flexible
  • If the day's deployments run over 7 hours, they need to contact their manager.
  • Techs are required to enter their time into PeopleSoft by end of day on Thursday.
    • If the time entered for Friday is not correct, the tech should update it by 4:30 in PeopleSoft or contact their manager.
    • If you need to call in sick, email both your manager and Dave Cloutier as soon as possible in the morning.
    • Request vacation and personal days (and preplanned sick days) via requests in PeopleSoft. Manager will approve (if the schedule allows for it) and enter it into the Google calendar
    • Generally, only one tech can be scheduled out for vacation at a time.
    • You are expected to have your phone with you and be accessible by call or text during working hours.
    • You are expected to read all your email every workday and respond in a timely manner.
    • You are expected to attend the daily stand up meeting at 10AM. If you are scheduled to be with at client, let you manager know ahead of time. Also, check in with your manager as soon as you are available to give your daily update.
    • You are expected to attend all meetings setup by Support Services management. If you cannot attend, you should respond so in a timely manner, with alternative date. Also, you are expected to keep you manager informed of any meetings.
    • In general, dress should be professional. On Friday’s jeans are allowed, but they should be Jeans workplace appropriate and professional. Please speak to your manager for team-specific dress code.
    • One (or optionally more) of the following should be worn during work hours: HUIT shirt, HUIT lanyard, or HUIT name badge. On certain occasions, you will be asked to wear your HUIT shirt.
    • Harvard University's Performance Management Process (PMP) is a key component of professional development, which is important for the individual employee and as a primary goal of our senior leadership team. Harvard’s performance management process has three components: planning, mid-year, and annual review.
    • Employees are expected to participate in the process by selecting goals, filling out the form and thoughtfully filling in your self-evaluation at mid-year and for your annual review.
    •  All PMP forms should be completed before the deadlines set by HUIT administration.

Time off

Communication

Meetings

Dress Code

PMP process

 

Appendics

Appendix A

 

Reach out email from Deployment Tech to customer 2 days before deployment

Hello (Customer Name),

I hope this email finds you well. I am the technician that is handling your upgrade on (date). Are you available to meet at (time)? Please let me know if that time doesn’t work.

I see that you are upgrading to a (computer model , is this correct? Is your office located at (office location)? If not, please provide the proper office location.

Below, you will find how the process works and information you can provide that will help with the process.

  • We will meet for about 15 mins, to gather information about your computer, applications, data, etc.
  • I will take your old computer back to my office to start the process.
  • Dependent upon the outcome of the process, I will return between 1-3pm to set up the new computer.

I see that you have requested the following applications.  If anything is missing, below, list the applications you will need to be reinstalled (if applicable, please have licenses available upon visit)). We will review this while I am there as well.

 (list programs from calendar entry)

Let me know if you have any questions. I can be reached via email or on my cell (tech number).

Best,

Appendix B

 

Imaging setup at 1033 Mass Ave.

The LAN used for imaging is vlan 689,  DLS:Imaging-Network-1033. It is connected to the switch on our floor mass1033-m-sw1#. The following jacks are on this VLAN:

M021D1M - Fa1/0/24

M022D1M - Fa1/0/32

M019D1M - Fa1/0/33

M088M - Fa1/0/39


 [CA1]April 18th

 

 

 

 

 

 

 

 

 

  • No labels