<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Restrict access to system command propmt</title><link>https://communities.bentley.com/products/administration/f/product-administration-forum/104179/restrict-access-to-system-command-propmt</link><description>Hi, 
 
 We have restricted use of the run command within Windows and hidden the C drive from users within explorer however users can fork out to a command window within Microstation by using the ! or % key-ins. This gives them access to the hidden C drive</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Restrict access to system command propmt</title><link>https://communities.bentley.com/thread/312374?ContentTypeID=1</link><pubDate>Tue, 27 Jan 2015 16:15:02 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:0979236b-54c3-46be-8993-92bf9d9bd090</guid><dc:creator>ColinTanswell</dc:creator><description>Hi,&lt;br /&gt;
&lt;br /&gt;
Restricted access to the run command is via group policy as is the hidden c drive within windows explorer. You can&amp;#39;t even enter c:\ within explorer. If you use the ! Keyin in Microstation then you can get to the c drive within the command prompt. I&amp;#39;m not from IT but a power user for CAD it is IT that has asked me the question to see if the keyin can be restricted.&lt;br /&gt;
&lt;br /&gt;
I didn&amp;#39;t know if there was a Microstation variable to restrict the ! Keyin but it seems not. It looks like a command filter application is the way to go.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Colin.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restrict access to system command propmt</title><link>https://communities.bentley.com/thread/312362?ContentTypeID=1</link><pubDate>Tue, 27 Jan 2015 15:45:56 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:8fa673d6-8bd0-4e8e-9735-928c4e8b3a89</guid><dc:creator>Jan Šlegr</dc:creator><description>&lt;p&gt;Hi Colin,&lt;/p&gt;
&lt;p&gt;in addition to Phil&amp;#39;s answer:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How do you restrict using command prompt? I have not tested it (I have only basic Windows admin knowledge), but using system policy should solve it.&lt;/li&gt;
&lt;li&gt;Hiding cannot be treated as a restriction in any way, it&amp;#39;s not its intention. Hidden folder is still fully accessible by definition. If you need another level of control, access rights asignment is a proper tool.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The monitor application mentioned by Phil could be the solution, but only for MicroStation. But in Windows there are plenty of places where Command Prompt can be started from ... and we are back at system policy and GAC.&lt;/p&gt;
&lt;p&gt;With regards,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Jan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restrict access to system command propmt</title><link>https://communities.bentley.com/thread/312338?ContentTypeID=1</link><pubDate>Tue, 27 Jan 2015 14:57:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:12fa152b-ebb0-483a-8e9b-1f711696dc9c</guid><dc:creator>Phil Chouinard</dc:creator><description>Two things come to mind... develop and use an application that filters the input queue for those key-ins and rejects them or take a look at disabling the command prompt through Group Policy (there are quite a number of hits on the internet for the latter, along with disclaimers about things to take into account).&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>