tag:blogger.com,1999:blog-5384857.post112832382345263577..comments2023-10-10T03:52:55.494+01:00Comments on Under The Stairs: Monad on Windows 2000Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5384857.post-85589137277680839002008-07-25T10:16:00.000+01:002008-07-25T10:16:00.000+01:00Thomas,The answer is no - see my later post at: ht...Thomas,<BR/><BR/>The answer is no - see my later post at: http://tfl09.blogspot.com/2008/07/no-virginia-powershell-on-windows-2000.htmlThomas Leehttps://www.blogger.com/profile/05591926562143348089noreply@blogger.comtag:blogger.com,1999:blog-5384857.post-17886770631773941202008-07-24T23:23:00.000+01:002008-07-24T23:23:00.000+01:00After some reasonable research and writing some sc...After some reasonable research and writing some scripts in PowerShell to capture aspects of our application for the purpose of revision control, deployment, and auditing, I went to improve performance by running the scripts on our production servers; too bad I didn't read the fine print that PowerShell doesn't run on Windows 2000.<BR/><BR/>That said, is there any way to salvage a sub-set of the assemblies / classes of PowerShell so that I don't have to home grow my own .NET connectors to WMI and ADSI?<BR/><BR/>It would have been nice if PowerShell would gracefully degrade on "down-level" systems; however, since it is part of code access security, I can see how one might not want to open that can of worms.<BR/><BR/>Sigh.<BR/><BR/>Thomas TriasAnonymoushttps://www.blogger.com/profile/09385514813612839351noreply@blogger.com