Jump to content

Registering DLLs for everyone who connects to Terminal Server

Guest Pearl

By Guest Pearl
in Windows NT Server

 Share

Recommended Posts

Guest Pearl

Guest Pearl

Posted
Posted

We have a Terminal Server 2003 which has MapBook installed. In order for all

the TS users to use MapBook a separate installation of DLLs using a batchfile

is required. We've tried to register the DLLs normally...that didn't work.

So, we let the TS administrator install the DLLs. That didn't work. So,

what is the way to register DLLs in Terminal Server so all users have access

to them?

  • Replies 5
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Eric Robinson

Guest Eric Robinson

Posted
Posted

Re: Registering DLLs for everyone who connects to Terminal Server

 

All you have to do is register them the normal way (regsvr32) and make sure

they are in a directory that all users can access. Have you tried running

filemon to see if your application is having trouble finding them or reading

them?

 

"Pearl" <Pearl@discussions.microsoft.com> wrote in message

news:CCD90BBD-8504-4B7A-B86A-5881B2D514B1@microsoft.com...

> We have a Terminal Server 2003 which has MapBook installed. In order for

> all

> the TS users to use MapBook a separate installation of DLLs using a

> batchfile

> is required. We've tried to register the DLLs normally...that didn't

> work.

> So, we let the TS administrator install the DLLs. That didn't work. So,

> what is the way to register DLLs in Terminal Server so all users have

> access

> to them?

Guest Pearl

Guest Pearl

Posted
Posted

Re: Registering DLLs for everyone who connects to Terminal Server

 

so, I can not use the batchfile execution to auto install the DLLs? I will

have to do it manually?

 

"Eric Robinson" wrote:

> All you have to do is register them the normal way (regsvr32) and make sure

> they are in a directory that all users can access. Have you tried running

> filemon to see if your application is having trouble finding them or reading

> them?

>

> "Pearl" <Pearl@discussions.microsoft.com> wrote in message

> news:CCD90BBD-8504-4B7A-B86A-5881B2D514B1@microsoft.com...

> > We have a Terminal Server 2003 which has MapBook installed. In order for

> > all

> > the TS users to use MapBook a separate installation of DLLs using a

> > batchfile

> > is required. We've tried to register the DLLs normally...that didn't

> > work.

> > So, we let the TS administrator install the DLLs. That didn't work. So,

> > what is the way to register DLLs in Terminal Server so all users have

> > access

> > to them?

>

>

>

Guest Pearl

Guest Pearl

Posted
Posted

RE: Registering DLLs for everyone who connects to Terminal Server

 

As it turns out, it appears the bat file provided to us by the vendor (ESRI)

does more than just register DLLs. It also modifies the registry :

 

REGEDIT4

 

 

 

; the first guid is the guid representing the component to register and the

second represents the component category

 

 

 

; Double click on this file from Explorer to automatically

 

; update the specified information for your component.

 

 

 

; Add ESRI Contents Views {089874FC-CC18-11D2-9F39-00C04F6BC78E}

 

;DSMapBookUIPrj.MapSeriesTab

 

[HKEY_CLASSES_ROOT\CLSID\{AC7622A7-6D66-4D2B-9AE0-EB70BD262B53}\Implemented

Categories\{089874FC-CC18-11D2-9F39-00C04F6BC78E}]

 

 

 

 

 

; Add ESRI MX Extensions {B56A7C45-83D4-11D2-A2E9-080009B6F22B}

 

;DSMapBookUIPrj.MapSeriesExt

 

[HKEY_CLASSES_ROOT\CLSID\{E918E787-8B4E-4D51-877C-AD67905C6109}\Implemented

Categories\{B56A7C45-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

;Add Toolbars to ESRI Mx CommandBars Category

({B56A7C4A-83D4-11D2-A2E9-080009B6F22B})

 

;DSMapBookUIPrj.MapSeriesBar

 

[HKEY_CLASSES_ROOT\CLSID\{B121B1BA-5420-464B-802A-7A6C89123093}\Implemented

Categories\{B56A7C4A-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

;Add Commands and Tools to ESRI MX Commands Category

({B56A7C42-83D4-11D2-A2E9-080009B6F22B})

 

;DSMapBookUIPrj.CreateMapBook

 

[HKEY_CLASSES_ROOT\CLSID\{DC395506-3391-4207-99D4-C70851BAE9EA}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.DSPageIdentifier

 

[HKEY_CLASSES_ROOT\CLSID\{1DA56C9C-4646-41B8-93CE-61AB6F04D982}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.clsMapGridButton

 

[HKEY_CLASSES_ROOT\CLSID\{122B316F-67A6-42D4-B76D-63BFB6210393}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.clsStringGridButton

 

[HKEY_CLASSES_ROOT\CLSID\{BBAF9983-58D2-40D7-A093-FE564EA8966E}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

It appears to be changing the HKey_Classes_root. Not sure that bearing that

has on the issue. Wish I had more to add.

 

 

 

"Pearl" wrote:

> We have a Terminal Server 2003 which has MapBook installed. In order for all

> the TS users to use MapBook a separate installation of DLLs using a batchfile

> is required. We've tried to register the DLLs normally...that didn't work.

> So, we let the TS administrator install the DLLs. That didn't work. So,

> what is the way to register DLLs in Terminal Server so all users have access

> to them?

Guest Pearl

Guest Pearl

Posted
Posted

RE: Registering DLLs for everyone who connects to Terminal Server

 

It appears that the BAT file does more than register DLLS. The vendor (ESRI)

provided the BAT file but it wasn't geared for TS:

 

REGEDIT4

 

 

 

; the first guid is the guid representing the component to register and the

second represents the component category

 

 

 

; Double click on this file from Explorer to automatically

 

; update the specified information for your component.

 

 

 

; Add ESRI Contents Views {089874FC-CC18-11D2-9F39-00C04F6BC78E}

 

;DSMapBookUIPrj.MapSeriesTab

 

[HKEY_CLASSES_ROOT\CLSID\{AC7622A7-6D66-4D2B-9AE0-EB70BD262B53}\Implemented

Categories\{089874FC-CC18-11D2-9F39-00C04F6BC78E}]

 

 

 

 

 

; Add ESRI MX Extensions {B56A7C45-83D4-11D2-A2E9-080009B6F22B}

 

;DSMapBookUIPrj.MapSeriesExt

 

[HKEY_CLASSES_ROOT\CLSID\{E918E787-8B4E-4D51-877C-AD67905C6109}\Implemented

Categories\{B56A7C45-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

;Add Toolbars to ESRI Mx CommandBars Category

({B56A7C4A-83D4-11D2-A2E9-080009B6F22B})

 

;DSMapBookUIPrj.MapSeriesBar

 

[HKEY_CLASSES_ROOT\CLSID\{B121B1BA-5420-464B-802A-7A6C89123093}\Implemented

Categories\{B56A7C4A-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

;Add Commands and Tools to ESRI MX Commands Category

({B56A7C42-83D4-11D2-A2E9-080009B6F22B})

 

;DSMapBookUIPrj.CreateMapBook

 

[HKEY_CLASSES_ROOT\CLSID\{DC395506-3391-4207-99D4-C70851BAE9EA}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.DSPageIdentifier

 

[HKEY_CLASSES_ROOT\CLSID\{1DA56C9C-4646-41B8-93CE-61AB6F04D982}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.clsMapGridButton

 

[HKEY_CLASSES_ROOT\CLSID\{122B316F-67A6-42D4-B76D-63BFB6210393}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

;DSMapBookUIPrj.clsStringGridButton

 

[HKEY_CLASSES_ROOT\CLSID\{BBAF9983-58D2-40D7-A093-FE564EA8966E}\Implemented

Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

 

 

 

 

 

It appears to be changing the HKey_Classes_root. Not sure that bearing that

has on the issue. Wish I had more to add.

 

 

 

"Pearl" wrote:

> We have a Terminal Server 2003 which has MapBook installed. In order for all

> the TS users to use MapBook a separate installation of DLLs using a batchfile

> is required. We've tried to register the DLLs normally...that didn't work.

> So, we let the TS administrator install the DLLs. That didn't work. So,

> what is the way to register DLLs in Terminal Server so all users have access

> to them?

Guest Eric Robinson

Guest Eric Robinson

Posted
Posted

Re: Registering DLLs for everyone who connects to Terminal Server

 

Those registry changes look harmless. Did you try my suggestion to see if

your app is actually loading (or attempting to load) the DLLs?

 

"Pearl" <Pearl@discussions.microsoft.com> wrote in message

news:36D47E3D-20B5-4B77-819B-40C316C00C81@microsoft.com...

> It appears that the BAT file does more than register DLLS. The vendor

> (ESRI)

> provided the BAT file but it wasn't geared for TS:

>

> REGEDIT4

>

>

>

> ; the first guid is the guid representing the component to register and

> the

> second represents the component category

>

>

>

> ; Double click on this file from Explorer to automatically

>

> ; update the specified information for your component.

>

>

>

> ; Add ESRI Contents Views {089874FC-CC18-11D2-9F39-00C04F6BC78E}

>

> ;DSMapBookUIPrj.MapSeriesTab

>

> [HKEY_CLASSES_ROOT\CLSID\{AC7622A7-6D66-4D2B-9AE0-EB70BD262B53}\Implemented

> Categories\{089874FC-CC18-11D2-9F39-00C04F6BC78E}]

>

>

>

>

>

> ; Add ESRI MX Extensions {B56A7C45-83D4-11D2-A2E9-080009B6F22B}

>

> ;DSMapBookUIPrj.MapSeriesExt

>

> [HKEY_CLASSES_ROOT\CLSID\{E918E787-8B4E-4D51-877C-AD67905C6109}\Implemented

> Categories\{B56A7C45-83D4-11D2-A2E9-080009B6F22B}]

>

>

>

>

>

> ;Add Toolbars to ESRI Mx CommandBars Category

> ({B56A7C4A-83D4-11D2-A2E9-080009B6F22B})

>

> ;DSMapBookUIPrj.MapSeriesBar

>

> [HKEY_CLASSES_ROOT\CLSID\{B121B1BA-5420-464B-802A-7A6C89123093}\Implemented

> Categories\{B56A7C4A-83D4-11D2-A2E9-080009B6F22B}]

>

>

>

>

>

> ;Add Commands and Tools to ESRI MX Commands Category

> ({B56A7C42-83D4-11D2-A2E9-080009B6F22B})

>

> ;DSMapBookUIPrj.CreateMapBook

>

> [HKEY_CLASSES_ROOT\CLSID\{DC395506-3391-4207-99D4-C70851BAE9EA}\Implemented

> Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

>

> ;DSMapBookUIPrj.DSPageIdentifier

>

> [HKEY_CLASSES_ROOT\CLSID\{1DA56C9C-4646-41B8-93CE-61AB6F04D982}\Implemented

> Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

>

> ;DSMapBookUIPrj.clsMapGridButton

>

> [HKEY_CLASSES_ROOT\CLSID\{122B316F-67A6-42D4-B76D-63BFB6210393}\Implemented

> Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

>

> ;DSMapBookUIPrj.clsStringGridButton

>

> [HKEY_CLASSES_ROOT\CLSID\{BBAF9983-58D2-40D7-A093-FE564EA8966E}\Implemented

> Categories\{B56A7C42-83D4-11D2-A2E9-080009B6F22B}]

>

>

>

>

>

> It appears to be changing the HKey_Classes_root. Not sure that bearing

> that

> has on the issue. Wish I had more to add.

>

>

>

> "Pearl" wrote:

>

>> We have a Terminal Server 2003 which has MapBook installed. In order for

>> all

>> the TS users to use MapBook a separate installation of DLLs using a

>> batchfile

>> is required. We've tried to register the DLLs normally...that didn't

>> work.

>> So, we let the TS administrator install the DLLs. That didn't work. So,

>> what is the way to register DLLs in Terminal Server so all users have

>> access

>> to them?

 Share
Go to topic listing
×
×
  • Create New...