Regional Server: Difference between revisions
Ttenbergen (talk | contribs) m (→2 - Call the [[eHealth ServiceDesk]]: substance cleanup) |
Ttenbergen (talk | contribs) m (cleaned out link to Conc info) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
The [[CCMDB. | The [[CCMDB.accdb]] and our sent data are located on the '''Regional Server''' | ||
* \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION | * \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION | ||
There is a shortcut on all laptop desktops called "Regional Server" - please leave it called so all laptops are the same and covering collectors know what to look for. | There is a shortcut on all laptop desktops called "Regional Server" - please leave it called so all laptops are the same and covering collectors know what to look for. | ||
Line 13: | Line 13: | ||
=== 2 - Call the [[eHealth ServiceDesk]] === | === 2 - Call the [[eHealth ServiceDesk]] === | ||
* The most common reason not to be able to access the regional server is something going wrong during the login process. Usually a re-boot will fix this. | * The most common reason not to be able to access the regional server is something going wrong during the login process. Usually a re-boot will fix this. | ||
* '''If a PC reboot does not fix your access to the '''regional server''', call the [[eHealth ServiceDesk]]''' | * '''If a PC reboot does not fix your access to the '''regional server''', call the [[eHealth ServiceDesk]]'''. [[:Category:IT Support | CCMDB IT Support]] cannot fix this, the problem will be fixed fastest if you call [[eHealth ServiceDesk]]. | ||
** tell the helpdesk that "this is '''not a mapping issue''' because we access the server using the '''UNC name'''" | ** tell the helpdesk that "this is '''not a mapping issue''' because we access the server using the '''UNC name'''" | ||
** if the server is running fine, and the network connection of your location to the rest of the | ** if the server is running fine, and the network connection of your location to the rest of the WRHA is up, then the problem might be with the way your account is set up; the help desk might they want to check how access rights should be set up, refer them to the instructions to set up a Regional data collector, as written by '''[[Sandy Kroeger]]''' from eHealth. | ||
== Requesting Access to the Regional Server == | == Requesting Access to the Regional Server == | ||
Line 25: | Line 25: | ||
== Regional Server Dependencies == | == Regional Server Dependencies == | ||
If the Regional Server changes locations all the automation accessing it needs to be updated: | If the Regional Server changes locations all the automation accessing it needs to be updated: | ||
* [[CCMDB. | * [[CCMDB.accdb]] - should be single location fix in in function regional_server now | ||
* [[News and Backup]] batch file | * [[News and Backup]] batch file | ||
* desktop shortcuts (see [[Laptop Setup]] for more info) | * desktop shortcuts (see [[Laptop Setup]] for more info) | ||
Line 31: | Line 31: | ||
* [[CCMDB Cleaner.mdb]] | * [[CCMDB Cleaner.mdb]] | ||
== Related Articles == | |||
{{Related Articles}} | |||
== Legacy Info == | == Legacy Info == | ||
{{Collapsable | |||
| always=Legacy Info | |||
| full= | |||
=== old regional server sbghnwfs0102 === | === old regional server sbghnwfs0102 === | ||
Until 2012-08 we used a different regional server. After we had ongoing difficulties connecting to it eHealth moved us over to a new one. The old one was | Until 2012-08 we used a different regional server. After we had ongoing difficulties connecting to it eHealth moved us over to a new one. The old one was | ||
Line 45: | Line 49: | ||
* ensure all have access; checklist is at {{Regionalserver|zzzchecklist.txt}} | * ensure all have access; checklist is at {{Regionalserver|zzzchecklist.txt}} | ||
* update [[Net use reg srv.bat]] (done, now maps to R: as well in case anyone had that hard-coded to the old regional server; needs to be rolled out with rest) | * update [[Net use reg srv.bat]] (done, now maps to R: as well in case anyone had that hard-coded to the old regional server; needs to be rolled out with rest) | ||
* change how regional server is accessed by [[CCMDB. | * change how regional server is accessed by [[CCMDB.accdb]] | ||
** linked tables - done | ** linked tables - done | ||
** sending - done | ** sending - done | ||
Line 105: | Line 109: | ||
* \\sbghnwfs0102\NSSVOL1\shared\ICU_DATA_COLLECTION\Documents | * \\sbghnwfs0102\NSSVOL1\shared\ICU_DATA_COLLECTION\Documents | ||
** versions | ** versions | ||
}} | |||
[[Category:IT Instructions]] | [[Category:IT Instructions]] | ||
[[Category:eHealth]] | [[Category:eHealth]] |
Latest revision as of 11:01, 2020 April 21
The CCMDB.accdb and our sent data are located on the Regional Server
- \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION
There is a shortcut on all laptop desktops called "Regional Server" - please leave it called so all laptops are the same and covering collectors know what to look for.
If you still have the old "Regional Server" shortcut please delete it.
Troubleshooting Regional Server
If you can't access the regional server, ie the shortcut on your desktop doesnt' get you there, then:
1 - Reboot
- If you can't access the regional server, the first thing to try is to re-boot.
- The most common reason not to be able to access the regional server is something going wrong during the login process. Usually a re-boot will fix this.
2 - Call the eHealth ServiceDesk
- The most common reason not to be able to access the regional server is something going wrong during the login process. Usually a re-boot will fix this.
- If a PC reboot does not fix your access to the regional server, call the eHealth ServiceDesk. CCMDB IT Support cannot fix this, the problem will be fixed fastest if you call eHealth ServiceDesk.
- tell the helpdesk that "this is not a mapping issue because we access the server using the UNC name"
- if the server is running fine, and the network connection of your location to the rest of the WRHA is up, then the problem might be with the way your account is set up; the help desk might they want to check how access rights should be set up, refer them to the instructions to set up a Regional data collector, as written by Sandy Kroeger from eHealth.
Requesting Access to the Regional Server
see Setting up a New Data Collector
What if I am missing the shortcut
Regional Server Dependencies
If the Regional Server changes locations all the automation accessing it needs to be updated:
- CCMDB.accdb - should be single location fix in in function regional_server now
- News and Backup batch file
- desktop shortcuts (see Laptop Setup for more info)
- Pagasa's Category: Batch Files
- CCMDB Cleaner.mdb
Related Articles
Legacy Info
Legacy Info |
old regional server sbghnwfs0102Until 2012-08 we used a different regional server. After we had ongoing difficulties connecting to it eHealth moved us over to a new one. The old one was
Moving to Regional Server will discontinue using #Twister altogether, so please ensure you don't refer to Twister after this is implemented. The old regional server was hosted at StBoniface; I don't think the new one is. Migration Checklist
TwisterCCMDB staff at HSC will sometimes refer to the Regional Server as "Twister". This is because HSC used to require a "door" (a gateway) with the sign "Twister" to access the Regional Server. However, this door also leads elsewhere (which might confuse the help desk), and the door is not used from other locations (which might confuse data collectors). To avoid confusion, use the term Regional Server. The actual address was \\Twister\icu\ Server name usage prior to changing to fully qualified domain name (FQDN)The Regional Server used to be accessed as:
A lot of locations are still set up with this link. However, notably at the Vic this set-up no longer works. All new laptops will be set up with the new address, \\sbghnwfs0102.ad.wrha.mb.ca\NSSVOL1\shared\icu_Data_Collection\, which includes the domain name ".ad.wrha.mb.ca". The full address should work everywhere, but wherever there is no problem this is not an urgent thing to change. 2010-08-20 Post-PDA ArchivingI have backed up old files to CD and removed them from the Regional Server. We used to use about 2.7GB and now use about 780MB. Specifically:
|