90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!
Solved
Powershell
Posted on 2011-09-20
Dear Experts;
I have a powershell that reads a list of computers and copies a file to their desktop. I need to add an if statment to this code that would see if the folder in C:\Program Files\Microsoft Office\Office12 (if computer has office 2007) exists in the target computer and if it does then copies the files in to the computer but if the folder does not exist then does not copy the file and moves on to the next computer in the text file. (the list of computers are in a text file)
FYI: I am a beginner in powershell and have no time to search for this so please HELP :)
$Computers = get-qadcomputer
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
try {$Copy = Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
if ($?){"$CompName Success" >> UpdateLog.txt}else{"$CompN
} #end try
Catch {}
Finally {}
} #end foreach
I have a powershell that reads a list of computers and copies a file to their desktop. I need to add an if statment to this code that would see if the folder in C:\Program Files\Microsoft Office\Office12 (if computer has office 2007) exists in the target computer and if it does then copies the files in to the computer but if the folder does not exist then does not copy the file and moves on to the next computer in the text file. (the list of computers are in a text file)
FYI: I am a beginner in powershell and have no time to search for this so please HELP :)
$Computers = get-qadcomputer
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
try {$Copy = Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
if ($?){"$CompName Success" >> UpdateLog.txt}else{"$CompN
} #end try
Catch {}
Finally {}
} #end foreach
-
5
3
9 Comments
The easiest way to test if the folder exists is to use the Test-Path cmdlet.
e.g. test-path -path "C:\Documents and Settings\NicoleH"
If the path exists the cmdlet return $True, otherwise $False so you can use it as the test condition in the if statement.
e.g. test-path -path "C:\Documents and Settings\NicoleH"
If the path exists the cmdlet return $True, otherwise $False so you can use it as the test condition in the if statement.
Can you provide the code please? Liek I said its urgent and I dont have time to figure it out myself.
This should do it. I changed it a bit because I haven't used try-catch a lot. Test-path will return true if the directory exists.
$Computers = get-qadcomputer
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
if (test-path "C:\Program Files\Microsoft Office\Office12") {
Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
"$CompName Success" >> UpdateLog.txt }
else {
"$CompName Failed" >> UpdateLog.txt }
} #end foreach
$Computers = get-qadcomputer
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
if (test-path "C:\Program Files\Microsoft Office\Office12") {
Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
"$CompName Success" >> UpdateLog.txt }
else {
"$CompName Failed" >> UpdateLog.txt }
} #end foreach
feaglin,
Would this code work if I have the name of computers in the textfile like computers.txt and does it go through each computer in the text file one by one?
Paul
Would this code work if I have the name of computers in the textfile like computers.txt and does it go through each computer in the text file one by one?
Paul
So like:
Please verify its pretty urgent
$Computers = get-content computernames.txt
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
if (test-path "C:\Program Files\Microsoft Office\Office12") {
Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
"$CompName Success" >> UpdateLog.txt }
else {
"$CompName Failed" >> UpdateLog.txt }
} #end foreach
Please verify its pretty urgent
$Computers = get-content computernames.txt
foreach ($Computer in $Computers){
$CompName = $Computer.name
"Attempting to copy files to $CompName..."
if (test-path "C:\Program Files\Microsoft Office\Office12") {
Copy-Item C:\\TEST.application "\\ComputerName\c$\Documen
"$CompName Success" >> UpdateLog.txt }
else {
"$CompName Failed" >> UpdateLog.txt }
} #end foreach
What I'm not sure is that if it doesn't go through each computer in the text file!
Can you verify this please?
Can you verify this please?
I'm on a different computer today that I can test this better on. It worked on my computer, so hopefully that matches your environment.
1- You will know the computers that you'll attempt to update because of line 5 and your logfile.
2- Line 4 I removed ".Name" from "$Computer". Getting the names from the text file means you're passing the names in as text instead of an AD object you have to specify the name on. If you switch back to getting the computernames from AD then you'll have to put the ".Name" back, like you have it in your original script.
3- Line 6 I changed to test the possible paths for 32 bit and 64 bit versions of Windows. I also fixed the path to check. You were testing the local computer and copying to a remote computer. I'm assuming you want to copy an application from your computer to computers on the network that have MS Office installed.
Note: The extra $() around $Compname is to get the variable properly recognized when it's in double quotes.
4- Line 7 I fixed the variable name (typo) and fixed it to work in a string.
1- You will know the computers that you'll attempt to update because of line 5 and your logfile.
2- Line 4 I removed ".Name" from "$Computer". Getting the names from the text file means you're passing the names in as text instead of an AD object you have to specify the name on. If you switch back to getting the computernames from AD then you'll have to put the ".Name" back, like you have it in your original script.
3- Line 6 I changed to test the possible paths for 32 bit and 64 bit versions of Windows. I also fixed the path to check. You were testing the local computer and copying to a remote computer. I'm assuming you want to copy an application from your computer to computers on the network that have MS Office installed.
Note: The extra $() around $Compname is to get the variable properly recognized when it's in double quotes.
4- Line 7 I fixed the variable name (typo) and fixed it to work in a string.
$Computers = get-content computernames.txt
foreach ($Computer in $Computers){
$CompName = $Computer
"Attempting to copy files to $CompName..."
if ( (test-path "\\$($CompName)\c$\Program Files\Microsoft Office\Office12") -or (test-path "\\$($CompName)\c$\Program Files (x86)\Microsoft Office\Office12") ) {
Copy-Item C:\\TEST.application "\\$($CompName)\c$\Documents and Settings\All Users\Desktop"
"$CompName Success" >> UpdateLog.txt }
else {
"$CompName Failed" >> UpdateLog.txt }
} #end foreach
Featured Post
Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.
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.
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 Already a member? Login.
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes. We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
Excel allows various different methods to link Excel files to each other. This includes relative paths, mapped drives (or the local drive) and UNC paths. UNC paths are the least robust of the three.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Did you know PowerShell can save you time with SaaS platforms? Simply leverage RESTfulAPIs to build your own PowerShell modules. These will kill repetitive tickets and tabs, using the command Invoke-RestMethod.
Tune into this webinar to learn how…
Suggested Courses
Course of the Month8 days, 8 hours left to enroll
595 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.