Project

General

Profile

« Previous | Next » 

Revision ae0a9e7c

Added by Patrick Plitzner almost 7 years ago

ref #6421 Add workaround to troubleshooting

View differences:

src/site/fml/troubleshooting.fml
79 79
			</answer>
80 80
		</faq>
81 81
		<faq id="windows_domain_active_directory">
82

  
83 82
			<question>Note for using the EDITor in a Windows Domain/Active directory</question>
84 83
			<answer>
85
			<p>Using the EDITor from a user account in an active directory is possible but in the case user profile folders are located on network folders, one of the following problems may occurr, when working with CDM databases:<p>
86
            <p>
87
            1) Problems are known, if the user profile path is an UNC path (e.g. "\\server\share").
88
            2) CDM Information may be written to the local machine's profile copy (if the %USERPROFILE% evironment variable is set respectively) and get lost during synchronization.
89
            </p>
90
            <p>
91
            If one of the described problems occurs, the following workaround can solve the problem:
92
            </p>
93
            <p>
94
            - Connect a network drive with the UNC path of your network profile root folder (if that is not already done within your group policies). (Make sure to check the option to reconnect the drive on the next login.)
95
            - Start the EDITor with the additional command line option "-Duser.home=I:\", where "I" should be replaced by the letter used for the network drive.
96
            </p>
97
            <p>
98
            Now all CDM Information will directly be accessed on the network resource. (Note that with such a configuration, it is not recommended to run multiple instances of the EDITor in different machines of the domain using the same user profile in parallel.)
99
            </p> 
84
    			<p>Using the EDITor from a user account in an active directory is possible but in the case user profile folders are located on network folders, one of the following problems may occurr, when working with CDM databases:
85
    			</p>
86
                <p>
87
                1) Problems are known, if the user profile path is an UNC path (e.g. "\\server\share").
88
                2) CDM Information may be written to the local machine's profile copy (if the %USERPROFILE% evironment variable is set respectively) and get lost during synchronization.
89
                </p>
90
                <p>
91
                If one of the described problems occurs, the following workaround can solve the problem:
92
                </p>
93
                <p>
94
                - Connect a network drive with the UNC path of your network profile root folder (if that is not already done within your group policies). (Make sure to check the option to reconnect the drive on the next login.)
95
                - Start the EDITor with the additional command line option "-Duser.home=I:\", where "I" should be replaced by the letter used for the network drive.
96
                </p>
97
                <p>
98
                Now all CDM Information will directly be accessed on the network resource. (Note that with such a configuration, it is not recommended to run multiple instances of the EDITor in different machines of the domain using the same user profile in parallel.)
99
                </p> 
100 100
			</answer>
101 101
		</faq>
102 102
	</part>

Also available in: Unified diff