| Author |
Message
|
| clindsey |
 Posted: Thu Jan 06, 2005 9:40 am Post subject: |
 |
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
WMQ 5.2 had some namespace issues with Terminal Services. If you do a search on this site for Terminal Services, you will probably find a lot of history.
WMQ 5.3 supports T.S.
Charlie |
|
| Back to top |
|
 |
| TimDroz |
| Posted: Thu Jan 06, 2005 9:55 am Post subject: |
|
|
Novice
Joined: 04 Mar 2004
Posts: 20
|
| Great news. Thanks all. I was really pounding my head against a brick wall on this one. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Jan 06, 2005 10:20 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Does MQ5.3+ have the same or similar issues with Terminal Services on 2003 Server?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Jan 06, 2005 11:15 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Jan 06, 2005 11:25 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Thanks...
I have some W2003 Servers that will be entering my environment soon. Not sure yet if I will be installing WMQ Server on any of them yet but I thought I would ask, just in case.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| oconnke1 |
| Posted: Tue Feb 08, 2005 9:21 pm Post subject: saveqmgr MQ 5.2 terminal services remote access |
|
|
Newbie
Joined: 04 Dec 2001
Posts: 5
Location: Los Angeles, California, USA
|
This same problem bothered me for a long time. It wasn't a Terminal Services problem, because the same symptoms occurred when I used PcAnywhere to login remotely. I knew the solution was to logon to the Win2K local console. The only problem was, I have Win2K servers spread all over the country. I finally came up with this trick... 
1. Put each of the commands you want to execute on the remote server into a .bat (.cmd) file. Use a separate .bat for each command.
2. If the command has an option to create an execution log file, specify it. This will make debugging easier if the command fails, because there may not be a command window you can examine afterwards.
3. Copy the .bat files into a directory on the remote server.
4. Open the MQ Services (not MQ Explorer) and click the plus (+) next to the queue manager for which you want to execute the command(s). This will cause the Custom Services folder to be exposed.
5. Right-click on the Custom Services folder and select New>>Custom Service. A "Create Custom Service" dialog window will appear, with the "Parameters" tab visible.
4. Type or paste the full path, including the .bat file name, into the "Start Command" field.
5. Give the custom service a reasonable name.
6. Leave "End Command" blank. (Some maintenance levels of MQ will copy the "Start Command" into the "End Command" when you leave this tab. Don't worry, it won't hurt anything.)
7. Select "Command" for "Execution.
8. Select "After" for "Startup"
9. Select the "General" tab.
10. Change the "Startup Type" to "Manual". If you don't, the command will run every time you start the queue manager.
11. Click the "Apply" button.
12. When you want to execute the command, just return to this window and click the Start button.
Voila, the command executes successfully. 
Now, why did this work and when you execute the same .bat file within a command window, it won't work. The answer is, Custom Services are executed under the authority of MUSR_MQADMIN, not the person who clicked the start button.
BTW
The reason I document this so precisely is, with a little imagination, you can use the same pattern for other purposes. For example, I couldn't get a WBI Adapter to start as a Windows Service, so I made it start as an MQ Custom Service. |
|
| Back to top |
|
|
| oconnke1 |
| Posted: Tue Feb 08, 2005 9:49 pm Post subject: Win2003 Server Terminal Services MQ 5.3 Command Authority |
|
|
Newbie
Joined: 04 Dec 2001
Posts: 5
Location: Los Angeles, California, USA
|
| csmith28 wrote: |
| Does MQ5.3+ have the same or similar issues with Terminal Services on 2003 Server? |
I've been running MQ 5.3 on Win2003 Server for 2 months and I've had no problems using a remote connection.
BTW
Microsoft basically rewrote the Terminal Services UI for Windows 2003 Server. They now call it "Remote Desktop Connection," and it's way cool. Get a copy from the Win2003 CD, or download it from Microsoft, and install it on your own computer. I run it on my Win2K Prof laptop and I remotely connect to both Win2K, running the old Terminal Services manager, and Win2003 Servers, running the new manager.
When you install it, you may be a little concerned that you'll lose all your TS connection files. Not to worry; the install converts them to .rdp files and places them into your Documents folder. This was a bit of a pain, until I created a sub-folder in Documents and named it "#Remote Desktop Locations" without the double quotes.
I moved all the .rdp files into this folder, except the default.rdp. The "#" on the front of the folder name causes it to sort to the top of the folder list, making it easy to find, and easy to remotely connect.  |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Feb 09, 2005 10:37 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Thanks oconnke1.
I have the new Terminal Services but apparently it has been decided that we will use RAdmin instead. It's been working pretty well so far. Sure beats the hell out of RemotelyPossible.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Feb 09, 2005 5:38 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| oconnke1 |
| Posted: Fri Feb 11, 2005 10:23 am Post subject: |
|
|
Newbie
Joined: 04 Dec 2001
Posts: 5
Location: Los Angeles, California, USA
|
Thanks, Peter. I didn't know about the "Run As" command.
I don't see a place to on the resultant dialog window to put runtime parameters, such as for runmqsc. Do you still use a bat/cmd file so they can be passed, or do you know another way to do it? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 11, 2005 1:34 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Dunno. I see my Sys Admin use this trick all the time, but have not had the need to play with Run As personally.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
