Desktop

Get Mapped Printer Information

koonz97 — Mon, 21 May 2012 17:59:10 GMT

Purpose:

This script can be used to collect the mapped network printer information from the users who are logged into the console of the Computer or Computers specified.

Required Modules:

PSRemoteRegistry, and Active Directory

Permission Requirements:

The user account that the script is run with needs to have administrative permissions on the workstations and permission to query Active Directory user accounts.

The computers firewall if enabled needs to allow it to be pinged, connections to WMI and also Remote Registry.

A user will need to be logged into the console so their mapped network printer information can be collected.

How the script functions:

Create a text file that contains a list of Computer names that you want to get the mapped network printers info for.

Execute the script and you will be prompted for the path to the text file that contains the list.

Connectivity will be verified to each of the computers by pinging each of them.

Via WMI it will check to see which user is logged into the computers that responded to the ping.

Next it will query Active Directory for the SID of each of the users that were currently logged into one of the active computers polled.

Using the users SID a Remote Registry query is created to enumerate the list of mapped network printers for the logged on user.

The Log files and CSV file containing the list of mapped printers is located in C:\temp\logs

FileNames:

MappedPrinters-(currentdate).csv -- Contains the list of mapped printers.

NoMappedPrinters-(currentdate).log -- Contains list of users that do not have network printers mapped on their computer.

NoReply-(currentdate).csv -- Contains list of computers that did not respond to ping.

NoUsrLoggedIn-(currentdate).log -- Contains list of computers that responded to ping but did not have a user logged into it.

RemoteRegNotRunning-(currentdate).log -- Contains a list of computers where the Remote Registry service is not running.

WmiError-(currentdate).log -- If there are computers that it is not able to connect to via wmi it will be listed here.

Install Multiple MSI files

Felipe — Wed, 04 Apr 2012 07:23:50 GMT

Usage:

.\InstallMSI.ps1 c:\temp\file1.msi "c:\temp\adobe acrobat\acro.msi" c:\users\admin\file2.msi

Visit: fbinotto.blogspot.com

Pin Shortcuts to Taskbar

Gerry Bammert — Sun, 11 Mar 2012 20:49:20 GMT

Help ==> Get-Help .\PinIconsToTaskbar.ps1 -Full
The script may be used in it-environments (e.g. at schools), where users work with a
mandatory profile (ntuser.man)
This script pins icons (=shortcuts) to the taskbar.

.NOTES
File Name      : PinIconsToTaskbar.ps1
Author         : Gerry Bammert, 11.03.2012
Prerequisite   : PowerShell V2, Windows 7
Copyright 2012 : There's no copyright, use it, modify it ... and post it back

Help ==> Get-Help .\PinIconsToTaskbar.ps1 -Full

The script may be used in it-environments (e.g. at schools), where users work with a
mandatory profile (ntuser.man)

This script pins icons (=shortcuts) to the taskbar.

There are two mandatory parameters: <PinIconsFolder> <Action verb>
<PinIconsFolder> That's the folder, where you collect the icons (=shortcuts).
This folder path can be a local path or an unc-path.
This folder might be placed in the user's homefolder,
so the user could manage the additional icons (=shortcuts) in the taskbar himself.
<Action verb> The verb has to be translated to your language.
english: "Pin to Taskbar"
german: "An Taskleiste anheften"
your language : " ....... "

You can find the verb in the shortcuts context menu.
Because icons on a network-path can't be pinned to the taskbar for security reasons,
the script copies the icons to a temporary path: LOCALAPPDATA\PinIcons\*.*

.NOTES

File Name      : PinIconsToTaskbar.ps1
Author         : Gerry Bammert, 11.03.2012
Prerequisite   : PowerShell V2, Windows 7
Copyright 2012 : There's no copyright, use it, modify it, enhance it ... and post it back

.LINK

Script is published at:
http://powershell.com/cs/media/default.aspx

.EXAMPLE

Example 1

PinIconsToTaskbar.ps1 <PinIconsFolder> <Action verb>
==> change the verb to the appropriate version of your language

English verbs:
PinIconsToTaskbar.ps1 "\\server1\homes$\$username\PinIconsFolder" "Pin to Taskbar"
PinIconsToTaskbar.ps1 "\\server1\homes$\$username\PinIconsFolder" "Unpin from Taskbar"

German verbs:
PinIconsToTaskbar.ps1 "\\server1\homes$\$username\PinIconsFolder" "An Taskleiste anheften"
PinIconsToTaskbar.ps1 "\\server1\homes$\$username\PinIconsFolder" "Von Taskleiste lösen"

.EXAMPLE

Example 2

PinIconsToTaskbar.ps1 <PinIconsFolder> <Action Verb>
==> change the verb to the appropriate version of your language

English verbs:
PinIconsToTaskbar.ps1 "Path to the PinIconsFolder" "Pin to Start Menu"
PinIconsToTaskbar.ps1 "Path to the PinIconsFolder" "Unpin from Start Menu"

German verbs:
PinIconsToTaskbar.ps1 "Path to the PinIconsFolder" "An Startmenü anheften"
PinIconsToTaskbar.ps1 "Path to the PinIconsFolder" "Von Startmenü lösen"

Run and time a script or command in the background

Carsten Schwartz — Mon, 20 Dec 2010 07:33:17 GMT

Running for example release scripts for releasing software, can have a large overhead if you print a lot of info in the console. At the same time you might want to time the relase to see how fast it us. Easy enough you run your command/ps1 file in the background using the start-job commandlet.

This script uses start-job together with Register-ObjectEvent to be able to time a job running in the background, for example:

PS >.\RunACommandInTheBackground.ps1 .\MakeRelease.ps1 https://svnserver:port/svn/OurProduct/trunk 613
Starting .\MakeRelease.ps1 https://svnserver:port/svn/OurProduct/trunk 613 as Job #1...
PS > Job #1 is finished...
Job Started: 10/29/2010 07:51:34
Job Stopped: 10/29/2010 07:54:39
Time Elapsed: 00:03:05.3862306
PS > Get-Job
PS >

The script runs a command or powershell script with any number of parameters in the background. The script creates a job runs it and shows start, stop and elapsed time when the job is terminated. The job is also removed from the Job list on termination.

Generic Delete Directory Contents

goodfth — Thu, 09 Sep 2010 19:36:36 GMT

This script deletes files from a directory path passed into it as a parameter and excludes some well known directories from being processed. The script also includes some simple logging to a file with the date/time it was executed and what path files were deleted from.

Open DialogBox by using .NET

Sylvain LESIRE — Tue, 23 Dec 2008 15:41:34 GMT

Next script to open file by using .NET

@Thomas Lee: Can you try it on W2k8? Can you tell us if it runs....

Open DialogBox by using Com Object

Sylvain LESIRE — Mon, 22 Dec 2008 09:52:27 GMT

This script permits to show you how to open a dialog box by using COM Object : UserAccounts.CommonDialog