Information of drives on a remote machine using powershell

[rahul1911]

Hello All,

I wanted to know if there is a method that I can use to get the hard drive information of a remote server using powershell 1.0. The WMI class that has been introduced in Powershell 2.0 does have the option to fetch the same information but the server environment that I work in does not have the option for Powershell 2.0 on the servers..

I do have powershell 2.0 on the machine from which i want to execute the command and fetch the information.

What I am looking for is to have the information like free space, name of the hard drives on a remote server.

Thanks in advance for any help that you can provide.

 

[Lorien]

Hi rahul1911,

See if the following thread helps: http://www.vistax64.com/powershell/208479-logical-disk-report-remote-servers.html. I honestly don't know if the difference in versions will permit this or make no difference or if another method is required.

If not, search through the Powershell section of the newsgroup to see if you can find what you need: PowerShell - Vista Forums

If that also doesn't help, try some other Powershell-specific forums:

http://www.scriptinganswers.com/forum2/forum_topics.asp?FID=27

http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/threads

http://www.powershellcommunity.org/Forums.aspx

I hope this helps.

Good luck!

 

[rahul1911]

Hello Lorien,

My apologies, I have been rather busy in some other things that I never noticed your reply. The links that you provided are great help but not in this topic. It does affect if both servers (executing server and remote server) are not on Powershell 2.0 as
-computername attribute was not present in Powershell 1.0 because of which if I execute the WMIobject class it only checks for all information on the local server and not on the remote one.

But anyways I do appreciate your effort to provide those links and they are really helpful in many of the other stuff that I need help with. I have even recommended them to my team and they seem very happy. Thanks.

 

[Lorien]

Hi Rahul1911,

I'm sorry the links didn't help with your problem (yet), but happy that they proved useful in other ways (perhaps now, perhaps in the future). It is quite possible that one of those links will lead you to a solution to THIS problem as those forums are specifically dedicated to Powershell and loaded with experts and experienced people who may well have posted the answer to your problem or can answer it if you post your problem in them (and I'd try them all - there's no telling which might strike gold). It occurs to me that your issue doesn't sound all that unusual that SOMEONE hasn't encountered it before and the solution is either posted in the threads or SOMEONE figured it out somehow and, if they did that, probably frequents at least one of those forums and may post a reply with a solution.

It was my pleasure - I'm glad I was able to help in some way (even if it didn't resolve your specific question). I researched the issue, found what little I could, realized you needed Powershell experts, and sought out the best forums I could find on the subject. Unfortunately, I very, very rarely use Powershell and then only for relatively simple tasks (I'm nowhere in your league), I do so only in a workgroup home network (I've never used it in a domain environment), have never tried using it for remote access (my clients are all individuals or small businesses who almost never have more than one location), and really haven't taken the time to fully understand the program's capabilities or how to use its more esoteric functions. I do not know the differences between v1.0 and v2.0, though apparently at least one exists which is causing this communication problem. I strongly suspect there is a solution, but I honestly barely understand the problem let alone what the solution might be (and whether it exists in changes to coding in v1.0 or v2.0), I know of nobody currently in these forums (since the Powershell newsgroup was closed) who has posted anything that exhibits an expertise in the program from whom I can request assistance (plus nobody else has posted a specific reply which suggests essentially the same thing).

In essence, I'm sorry we can't assist you with your specific question, but have confidence that one of the forums specializing in Powershell that I provided will be able to help you.

Thanks for the feedback - it is much appreciated.

Good luck and best wishes!