Regional Server: Difference between revisions

Line 25:

* All the settings that generate a trust relationship between Microsoft Access/Windows and the network directory that holds the data collected () are applied via a Group Policy called "WRK_ICFG_REG_CCMDB Laptops" that gets applied and/or updated every time the computer logs into the WRHA network (as long as the computer is connected to the network at the moment of logging in).

* 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.

=== 3 - 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]]'''. It could be either a problem with the server itself or with the network connection to the server (the latter is common at [[:Category:Concordia Hospital Office | Concordia]]). [[: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'''"

@@ Line 25: / Line 25: @@
 * All the settings that generate a trust relationship between Microsoft Access/Windows and the network directory that holds the data collected () are applied via a Group Policy called "WRK_ICFG_REG_CCMDB Laptops" that gets applied and/or updated every time the computer logs into the WRHA network (as long as the computer is connected to the network at the moment of logging in).
-* 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.
 === 3 - 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]]'''. It could be either a problem with the server itself or with the network connection to the server (the latter is common at [[:Category:Concordia Hospital Office | Concordia]]). [[: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'''"