165 reputation
17
bio website
location
age
visits member for 2 years, 1 month
seen Aug 6 at 17:34

Jul
2
awarded  Curious
Jun
7
asked RemoteApp Security Warning
May
23
awarded  Enthusiast
May
18
accepted How can I delete this ODBC?
May
18
answered How can I delete this ODBC?
May
17
awarded  Tumbleweed
May
17
asked Hide Network Icon in File Explorer on Server 2012
May
16
revised Mapped Drive by OU
deleted 2 characters in body
May
16
revised Mapped Drive by OU
formatting
May
16
asked Mapped Drive by OU
May
14
awarded  Commentator
May
14
comment ODBCs by Application
@tegbains A few days ago, yes. They are slow to get the ball rolling for this case, but they did tell me yesterday via email that they want to create an advisory case to pursue this (I initally reported via PartnerSource as a break-fix issue). I don't know where MSFT is or what they are doing at this point, but eventually they will probably help.
May
12
comment ODBCs by Application
As an administrator, it is easy to lock-down which GP application can be launched by which user. And user DSNs can be specified to limit which users can access which SQL instances/ODBCs/DSNs. However, in the case of a user with access to multiple GP applications and multiple SQL instance (ex. a power user), why should he/she be able to run "GP application A" with "SQL instance B"? I should not be able to do this. GP A should match up with SQL A, GP B with SQL B, and so forth...a 1:1 relationship.
May
12
comment ODBCs by Application
A GP instances requires (1) a unique GP installation directory and Dynamics.exe application, and (2) a unique SQL instance (not database, I truly mean SQL instance--as in a unique install of SQL). If a user launches a GP application on a server, when they attempt to login, they will be prompted to select to which "Server" (meaning SQL instance/ODBC) they want to connect.
May
12
revised ODBCs by Application
added 8 characters in body
May
11
asked ODBCs by Application
May
10
asked How can I delete this ODBC?
Apr
26
accepted Name Mismatch - Incorrect Remote Computer Name
Apr
25
awarded  Supporter
Apr
22
comment Name Mismatch - Incorrect Remote Computer Name
Well, how come there is no issue with a mismatch related to the other servers--none of which have an explicit listing within the certificate which includes their private IP addresses? I've taken the same approach for all servers, but four of them work fine, and one of them gives this name mismatch warning/error.