a:64:{s:15:"comment_post_ID";s:4:"2980";s:14:"comment_author";s:5:"mitch";s:20:"comment_author_email";s:17:"mmarks4@gmail.com";s:18:"comment_author_url";s:0:"";s:15:"comment_content";s:4067:"[Posted and mailed] 

Hi, Tom,

I noticed this item in your report, and I might be able to clarify somewhat:

Slight addendum from the lab (partially for my own remembering):
Computer 15 actually has two asset tags and looks like it was already joined to the instr domain but under a slightly different scheme (U at the end).  

Yes, at many school there will be some computers with two different asset tags affixed.  This came about when a new consulting company was working with CPS ITS, instituted a new asset scheme, and thought it important enough [or lucrative enough] to warrant going around and putting new-style asset tags on the computer workstations then already installed and trackable in the schools.  

When there are two, the larger ones (about 1 in. X 2.5 in.), with more info printed on them [and 9-digit asset numbers] are the old ones; while the smaller ones (about 0.25 in. X 1 in.), with less info printed on them [and 8-digit asset numbers] are the newer ones.  

Connected with that, there were at least three "eras" of schema for computer names:

(a) I 1234 W 123456789
(b) I 1234 W 12345678 U
(c) I 12345 W 12345678

The switch from (a) to (b) was done at the time of the switch of physical asset tag and style.  Since the number was a digit shorter, the full name was padded with that final "U" to keep the whole name at 15 characters.  (And probably "U" was chosen because the consultants in question were Unisys.)

Later, for many purposes including several technology contexts (but not all), schools began using 5-digit unit numbers in place of the 4-digit legacy unit numbers.  When this became part of the computer naming standard, the 8-digit asset numbers plus the two letters would yield 15-character computer names without the "U" padding, giving schema (c).  

  --

On the matter of Deep Freeze, it sounds like you've got it under control (except maybe for the wrong-school units).  Just remember that any changes made manually, to a computer in a DF *frozen* state, will be automatically rolled-back the next time it is rebooted.  Patches and updates pushed from ITS during overnight maintenance periods *do* find their way into permanent configuration of even the frozen computers -- we don't know for sure if they literally are remotely thawed, restarted, patched, and re-frozen; or if they have a way of "injecting" the patches into the frozen image directly.  

A school that has been using DF for a while may have computers with different versions of DF installed, including different passwords.  The main difference would be in the part that uses the school's unit number: try substituting the old 4-digit number for the 5-digit one, or vice versa.  
  OTOH, if the computers were brought from a different school, then it may be exactly as you say, that they have the DF setup from their original school.  If that school is known, maybe the DF password can be predicted.  Another approach is to run a Deep Freeze Enterprise Console, which could pick up those computers if they are on the local network and allow thawing them from the console without using the password.  (And once thawed, the DF can be replaced by a local new installation.)  You might want to check with Russ on what approach he will be taking with these.

  -- 

On the need for mice:  As I think I mentioned to you in connection with keyboards, usually CUIP has a few extra parts around and can put them in a school if it helps clear up something.  But we also want to encourage schools to realize they need to invest in maintenance costs for their computers, including spares for these peripherals.  Russ probably has in mind which approach would be appropriate at this time for these mice at Burke.  But if it's getting to be a pain and you want to solve it with a few replacement mice, you're welcome to stop by the CUIP office and take a couple mice for use at your school.  The only sticky point about that is finding a time when the office is open -- generally all day Monday will be good.  

Cheers,

  ==Mitch";s:12:"comment_type";s:0:"";s:14:"comment_parent";s:1:"0";s:7:"user_ID";s:1:"0";s:7:"user_ip";s:12:"75.21.85.225";s:10:"user_agent";s:108:"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11";s:8:"referrer";s:48:"http://reporting.cuip3.org/2012/11/week-3-burke/";s:4:"blog";s:26:"http://reporting.cuip3.org";s:9:"blog_lang";s:2:"en";s:12:"blog_charset";s:5:"UTF-8";s:9:"permalink";s:48:"http://reporting.cuip3.org/2012/11/week-3-burke/";s:21:"akismet_comment_nonce";s:6:"passed";s:11:"POST_author";s:5:"mitch";s:10:"POST_email";s:17:"mmarks4@gmail.com";s:8:"POST_url";s:0:"";s:12:"POST_comment";s:4071:"[Posted and mailed] 

Hi, Tom,

I noticed this item in your report, and I might be able to clarify somewhat:

Slight addendum from the lab (partially for my own remembering):
Computer 15 actually has two asset tags and looks like it was already joined to the instr domain but under a slightly different scheme (U at the end).  

Yes, at many school there will be some computers with two different asset tags affixed.  This came about when a new consulting company was working with CPS ITS, instituted a new asset scheme, and thought it important enough [or lucrative enough] to warrant going around and putting new-style asset tags on the computer workstations then already installed and trackable in the schools.  

When there are two, the larger ones (about 1 in. X 2.5 in.), with more info printed on them [and 9-digit asset numbers] are the old ones; while the smaller ones (about 0.25 in. X 1 in.), with less info printed on them [and 8-digit asset numbers] are the newer ones.  

Connected with that, there were at least three "eras" of schema for computer names:

(a) I 1234 W 123456789
(b) I 1234 W 12345678 U
(c) I 12345 W 12345678

The switch from (a) to (b) was done at the time of the switch of physical asset tag and style.  Since the number was a digit shorter, the full name was padded with that final "U" to keep the whole name at 15 characters.  (And probably "U" was chosen because the consultants in question were Unisys.)

Later, for many purposes including several technology contexts (but not all), schools began using 5-digit unit numbers in place of the 4-digit legacy unit numbers.  When this became part of the computer naming standard, the 8-digit asset numbers plus the two letters would yield 15-character computer names without the "U" padding, giving schema (c).  

  --

On the matter of Deep Freeze, it sounds like you've got it under control (except maybe for the wrong-school units).  Just remember that any changes made manually, to a computer in a DF *frozen* state, will be automatically rolled-back the next time it is rebooted.  Patches and updates pushed from ITS during overnight maintenance periods *do* find their way into permanent configuration of even the frozen computers -- we don't know for sure if they literally are remotely thawed, restarted, patched, and re-frozen; or if they have a way of "injecting" the patches into the frozen image directly.  

A school that has been using DF for a while may have computers with different versions of DF installed, including different passwords.  The main difference would be in the part that uses the school's unit number: try substituting the old 4-digit number for the 5-digit one, or vice versa.  
  OTOH, if the computers were brought from a different school, then it may be exactly as you say, that they have the DF setup from their original school.  If that school is known, maybe the DF password can be predicted.  Another approach is to run a Deep Freeze Enterprise Console, which could pick up those computers if they are on the local network and allow thawing them from the console without using the password.  (And once thawed, the DF can be replaced by a local new installation.)  You might want to check with Russ on what approach he will be taking with these.

  -- 

On the need for mice:  As I think I mentioned to you in connection with keyboards, usually CUIP has a few extra parts around and can put them in a school if it helps clear up something.  But we also want to encourage schools to realize they need to invest in maintenance costs for their computers, including spares for these peripherals.  Russ probably has in mind which approach would be appropriate at this time for these mice at Burke.  But if it's getting to be a pain and you want to solve it with a few replacement mice, you're welcome to stop by the CUIP office and take a couple mice for use at your school.  The only sticky point about that is finding a time when the office is open -- generally all day Monday will be good.  

Cheers,

  ==Mitch

";s:11:"POST_submit";s:14:"Submit Comment";s:20:"POST_comment_post_ID";s:4:"2980";s:26:"POST_akismet_comment_nonce";s:10:"2ef0fb45f5";s:15:"SERVER_SOFTWARE";s:6:"Apache";s:11:"REQUEST_URI";s:21:"/wp-comments-post.php";s:9:"AUTH_TYPE";s:5:"Basic";s:14:"CONTENT_LENGTH";s:4:"4537";s:12:"CONTENT_TYPE";s:33:"application/x-www-form-urlencoded";s:13:"DOCUMENT_ROOT";s:57:"/home/cuipmar4/public_html/blogs/standalone-WPs/reporting";s:17:"GATEWAY_INTERFACE";s:7:"CGI/1.1";s:11:"HTTP_ACCEPT";s:63:"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8";s:19:"HTTP_ACCEPT_CHARSET";s:30:"ISO-8859-1,utf-8;q=0.7,*;q=0.3";s:20:"HTTP_ACCEPT_ENCODING";s:17:"gzip,deflate,sdch";s:20:"HTTP_ACCEPT_LANGUAGE";s:14:"en-US,en;q=0.8";s:18:"HTTP_CACHE_CONTROL";s:9:"max-age=0";s:15:"HTTP_CONNECTION";s:10:"keep-alive";s:11:"HTTP_COOKIE";s:0:"";s:9:"HTTP_HOST";s:19:"reporting.cuip3.org";s:11:"HTTP_ORIGIN";s:26:"http://reporting.cuip3.org";s:12:"HTTP_REFERER";s:48:"http://reporting.cuip3.org/2012/11/week-3-burke/";s:15:"HTTP_USER_AGENT";s:108:"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11";s:4:"PATH";s:13:"/bin:/usr/bin";s:11:"PHP_AUTH_PW";s:0:"";s:13:"PHP_AUTH_USER";s:3:"nsp";s:12:"QUERY_STRING";s:0:"";s:15:"REDIRECT_STATUS";s:3:"200";s:11:"REMOTE_ADDR";s:12:"75.21.85.225";s:11:"REMOTE_PORT";s:5:"65070";s:11:"REMOTE_USER";s:3:"nsp";s:14:"REQUEST_METHOD";s:4:"POST";s:15:"SCRIPT_FILENAME";s:78:"/home/cuipmar4/public_html/blogs/standalone-WPs/reporting/wp-comments-post.php";s:11:"SCRIPT_NAME";s:21:"/wp-comments-post.php";s:11:"SERVER_ADDR";s:14:"174.127.110.33";s:12:"SERVER_ADMIN";s:29:"webmaster@reporting.cuip3.org";s:11:"SERVER_NAME";s:19:"reporting.cuip3.org";s:11:"SERVER_PORT";s:2:"80";s:15:"SERVER_PROTOCOL";s:8:"HTTP/1.1";s:16:"SERVER_SIGNATURE";s:0:"";s:9:"UNIQUE_ID";s:24:"ULE6g9HsR2MAC6P9-YgAAAAC";s:8:"PHP_SELF";s:21:"/wp-comments-post.php";s:12:"REQUEST_TIME";s:10:"1353792132";s:4:"argv";s:0:"";s:4:"argc";s:1:"0";s:25:"comment_post_modified_gmt";s:19:"2012-11-21 17:57:25";}