Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 285
  • Last Modified:

Command line in domain working XP client

Hi Experts!

First of all I would like to say I have already spent hours on solving below problem without effect!

I have a problem with all of the XP clients working in domain enviornment. The DC is run on Windows Small Business Server 2003 R2.

It is only possible to run command line (cmd) on local machine when a user is granted local Administrator rights (has to be in local Administrators group). And I need cmd to be run on clients to make them able to work with an old DOS-mode software run from a mapped disc.

In case he has no local Admin rigths trying to run cmd gives a pop-up error message:

"XP - 16 bit MS-DOS Subsystem error" - and so on...

Is it possible to make a user without these rights, logged to the domain using XP client, run cmd??

Hope you will helping me solution of that! Thx in advance!
0
pietia336
Asked:
pietia336
1 Solution
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Curious: Symantec installed? We have seen 16 bit MS-DOS Subsystem error:
http://blog.mpecsinc.ca/2008/09/xp-16-bit-ms-dos-subsystem-error.html

Just an off chance possibility.

Philip
0
 
pietia336Author Commented:
Yeah, Symantec is running, but the problem occurs also on machines without it.

However now I am able to run CMD, but any trail of running DOS apps gives:

"XP - 16 bit MS-DOS Subsystem error"

"C:\DOCUME~1\here is a username\Local~1\Temp\. A temporary file needed for the
initialization could not be created or could not be written to. Make sure
that the directory path exists, (it does) and disk space is available (it
is). Choose 'Close' to terminate the application.
"

Any clues???
0
 
McKnifeCommented:
To see what is really going on, download and use filemon and/or regmon for logging purposes.
0
 
Hisham_ElkouhaCommented:
It is better in you change the security setting of the old software ( the .exe file of the software
) that your client use , and permit the doamin users full controll for this software
0
 
pietia336Author Commented:
It wasn't the issue of security settings of the old .exe file nor the Symantec problem..

Probably some registry keys of old software (dunno which one at all?!?!) installations as the FULL REINSTALL OF XP clients did help and now everything is fine.

On one of the laptops however the symantec solution helped, but the 16bit subsystem error description given by the .exe file was exactly the same as in the document provided by MPEC SInc, so THX!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now