On one of the discussions on Slashdot.org regarding Windows Automation there was some quite useful that I had to collect for my own selfish purposes:By: thalakan (14668) on Friday May 06, @07:42PM PowerShell. The only tool that knows how to talk to all the different frameworks in Windows is PowerShell. No other tool can talk to .NET, COM, WMI, native APIs (via P/Invoke), and external studio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool. Other tools:System update readiness tool: http://support.microsoft.com/kb/947821/en-us [Microsoft.com]
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en [Microsoft.com]
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563 [microsoft.com]
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20 [microsoft.com]
ollydbg: http://www.ollydbg.de/ [ollydbg.de]
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062 [microsoft.com]
Windows Management Framework: http://support.microsoft.com/kb/968929 [microsoft.com]
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff [microsoft.com]
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en [microsoft.com]
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5D [microsoft.com] Other comments:By bertok (226922) writes: on Friday May 06, @08:11PMEssentially, for newer versions of Exchange and SharePoint, PowerShell is the only scripting option, and is excellent. For older versions, you don't have a lot of options, but you can probably call COM APIs using PowerShell as well, but the effort is a lot higher. The APIs exposed by Exchange (e.g.: MAPI) are hideous. SharePoint can be managed via direct SQL database queries from anything, with some care. Read more: Windows Azure Tribes
QR:
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en [Microsoft.com]
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563 [microsoft.com]
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20 [microsoft.com]
ollydbg: http://www.ollydbg.de/ [ollydbg.de]
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062 [microsoft.com]
Windows Management Framework: http://support.microsoft.com/kb/968929 [microsoft.com]
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff [microsoft.com]
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en [microsoft.com]
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5D [microsoft.com] Other comments:By bertok (226922) writes: on Friday May 06, @08:11PMEssentially, for newer versions of Exchange and SharePoint, PowerShell is the only scripting option, and is excellent. For older versions, you don't have a lot of options, but you can probably call COM APIs using PowerShell as well, but the effort is a lot higher. The APIs exposed by Exchange (e.g.: MAPI) are hideous. SharePoint can be managed via direct SQL database queries from anything, with some care. Read more: Windows Azure Tribes
QR:
Posts
0 comments:
Post a Comment