Changing a Laptop identifier: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m New page: The location of a laptop (set in L_Settings) has a bearing on various cross checks, output locations etc. Therefore, to change it all the related things need to be accounted for. ==C... |
TOstryzniuk (talk | contribs) mNo edit summary |
||
| Line 17: | Line 17: | ||
[[Category: IT Instructions]] | [[Category: IT Instructions]] | ||
[[Category: Site and Location]] | |||
Revision as of 17:56, 2010 January 5
The location of a laptop (set in L_Settings) has a bearing on various cross checks, output locations etc. Therefore, to change it all the related things need to be accounted for.
Check List
As of today this is only brainstorming, this list has not been tested. Trish, can you think of anything else? Ttenbergen 19:22, 9 December 2009 (CST)
We’ll need to
- Add a folder regional_server\programs\<new name> (rather than re-name, to facilitate backing out if we can’t finish)
- Add a folder regional server\data\<new name>
- Update the information in s_locations, and any other tables
- Likely some fixes for the .mdbs in the output folder to fix queries etc.
- Ensure that there is no code specifically mentioning the current location of the laptop (e.g. the long stay warning)
- find/search through all the modules for the current name
- address all finds; note: just changing the find to the new name may lead to undesired results, make sure the change is the right thing to do.
- make sure that the location name is not mentioned in any of the queries; I can't think of a nice way to automate this.
- change the location in L_Settings
- get local collector to send, and make sure all arrived, incl. in output DBs