Quantcast
Channel: ConfigMgr 2012 - Powershell Right Click Tools
Viewing all 140 articles
Browse latest View live
↧

Reviewed: Now Micro Right Click Tools 2.0 (Mar 10, 2014)

March 10, 2014, 7:14 am
$
0
0
Rated 5 Stars (out of 5) - Hey Ryan, I love this tool you have created. One question, is it possible to remove the hierarchy of the menu so when i right click a client object, I dont have to to maneuver under "Now Micro Right Click Tools ->" ? Is it possible to throw your right-click menus (Client Tools/Client Actions/Console Tools) right under the main right-click menu? Thanks!
↧
Search

New Post: How can I remove the Collection Tools?

April 15, 2014, 9:38 am
$
0
0
I love the RightClick Tools, but I'm afraid of what could happen if someone tried to restart our "all workstations" collection and rebooted 35,000 devices.

Is there anything that can be done to configure the tools so it doesn't display any Collection Tools? Or at least how can I hide/disable certain "tools"?

Thank you!
↧
↧

New Post: Right click tools not working at all

April 15, 2014, 1:53 pm
$
0
0
We are having the same issue here but haven't seen any replies on this issue yet. DotNET 4.5 is installed as well as Windows Management Framework 3.0 (PowerShell 3.0). The right click tools install fine, but when any of them are clicked on, the console quickly flashes and nothing happens. Any help on the issue would be appreciated.
↧

Created Unassigned: Multiple Context Menu Entries für Right Click Tools [10]

April 17, 2014, 2:44 am
$
0
0
For any item moved to a newly created subfolder hierarchy level (e.g. below applications in software library) and right-clicked at a new Right Click Tools context menu entry is appended.
The multiple entries disappear if the SCCM Console is restarted.
↧

Commented Unassigned: "Error launching Powershell Script" [9]

April 17, 2014, 9:19 am
$
0
0
Hello, I've installed .Net 4.5, Powershell 3.0 and then right click tools 2.0. I see the right click menu, however, upon launching action, I get "Error launching Powershell Script". Anyone have a workaround or solution???
Comments: I'm running into the same issue. I'm wondering if I need any of the older .Net packages installed since I don't have 1.0 or 1.1 currently.
↧
↧

Commented Unassigned: "Error launching Powershell Script" [9]

April 17, 2014, 9:43 am
$
0
0
Hello, I've installed .Net 4.5, Powershell 3.0 and then right click tools 2.0. I see the right click menu, however, upon launching action, I get "Error launching Powershell Script". Anyone have a workaround or solution???
Comments: Hmm, I haven't heard of this problem before. The message "Error launching Powershell script." comes from the vbs file I have launching it. The file simply runs: Powershell -sta -ExecutionPolicy Bypass -File Filename.ps1 arguments Open Powershell as an admin and try running this command: Get-ChildItem "C:\Program Files (x86)\Now Micro\Right Click Tools" | Unblock-File Your group policy might be blocking it, so that would unblock it.
↧

Commented Unassigned: Multiple Context Menu Entries für Right Click Tools [10]

April 17, 2014, 10:01 am
$
0
0
For any item moved to a newly created subfolder hierarchy level (e.g. below applications in software library) and right-clicked at a new Right Click Tools context menu entry is appended.
The multiple entries disappear if the SCCM Console is restarted.
Comments: I've seen that issue also. I believe it has something to do with us using a custom dll file for our own icon. I don't know of any way to fix it.
↧

Commented Unassigned: Installation issue [8]

April 17, 2014, 10:01 am
$
0
0
I am trying to install right click tools 1.4.1. The tools install without any errors. I dont have any menu options within the SCCM console. Windows 2008 R2 server, SCCM version 5.0.7804.1400. Ideas?

Thanks.
Comments: Try installing the newest version.
↧
Search

Closed Unassigned: Installation issue [8]

April 17, 2014, 10:01 am
$
0
0
I am trying to install right click tools 1.4.1. The tools install without any errors. I dont have any menu options within the SCCM console. Windows 2008 R2 server, SCCM version 5.0.7804.1400. Ideas?

Thanks.
↧
↧

New Post: Right click tools not working at all

April 17, 2014, 10:05 am
$
0
0
What is your execution policy in the x86 version of Powershell? Open Windows Powershell (x86) and check that policy. Change it to unrestricted if it is restricted and see if that solves your problem.
↧

New Post: How can I remove the Collection Tools?

April 17, 2014, 10:06 am
↧

New Post: Right click tools not working at all

April 17, 2014, 12:00 pm
$
0
0

These are my settings from x86 PowerShell. A co-worker has the same settings and his right click tools are working. So must be something else.

↧

Edited Unassigned: Multiple Context Menu Entries für Right Click Tools [10]

April 22, 2014, 9:39 am
$
0
0
For any item that is moved to a newly created subfolder hierarchy level (e.g. below applications in software library) a new Right Click Tools context menu entry is appended.
The multiple entries disappear if the SCCM Console is restarted.
↧
↧

New Post: Licensing Question

April 24, 2014, 5:54 am
$
0
0
Ryan,

The license in the install "Right Click Tools EULA.rtf" is quite different and significantly more restrictive then the "Apache License 2.0 (Apache)" shown in the License tab here on CodePlex.

Could you clarify what applies to the Right Click Tools? I really like the tools you have created, but I will need to uninstall them if the license continues to be "Right Click Tools EULA.rtf".

Thank you for your work on these tools. They are exceptional.

Thanks,
Tom
↧

New Post: Licensing Question

April 24, 2014, 7:49 am
$
0
0
The right click tools version 2.0 have the EULA distributed with them and they follow that EULA. The previous versions do not and follow the Apache License.

What in the license keeps you from having the tools installed? It is just restrictive on changes and re-distribution.

I also see that I can't change the EULA on CodePlex, so to avoid confusion I'm going to keep the Now Micro Right Click Tools (the ones covered by the EULA) on the Now Micro site, and the Powershell Right Click Tools (the ones that are open source) on Codeplex. I'll change that later today.
↧
Search

New Post: Licensing Question

April 30, 2014, 5:58 am
$
0
0
Sorry for the delay in responding.

The company I work for requires that all licenses go through a legal review. Quite a hassle, but I was pretty sure the Apache license was already reviewed or would sail right through.

The problems I have with the license are;
1) There can only be one archive copy and it can't be on a hard drive.
2) I can't copy or publish, install on other systems.
3) "The Restrictions on Use" that allows you to install and use the software on any number of systems conflicts the "License Grant" that stipulates 1 & 2 above.
4) I can't tweak any of the .ps1 files if I want per "Restrictions on Alteration".
5) "Restrictions on Copying" again states I can't have a copy on a hard drive.

This pretty much would be a nightmare getting through our legal review. I can't create an install on SCCM to deploy for our help desk and others. It would be extremely difficult to make sure there wasn't an extra copy of the msi laying around somewhere on a hard drive.

Again, I must say the tools are exceptional. Sorry if I have caused you issues. I was really hoping I could the Apache license and use these tools. When I have time I will look at the earlier version to see if I can use them, but I am guessing they will not have what I need.

Thanks,
Tom
↧

New Post: Schedule Restart or Shutdown - Prompt Issue

April 30, 2014, 5:22 pm
$
0
0
Hi Ryan
Firstly great set of tools. Much better then some of the alternatives.

I'm testing a few of the features and have run across an issue with the client scheduled restart or shutdown. When using the prompt user function the restart/shutdown does not occur nor does a prompt appear even though the scheduled task reports it runs successfully on the client.

I've tried running the task action in a command window and see the same problem - it creates a temp task and removes it then just complete with no further action. Removing the /schtask c:\windows\ConfigMgr_Shutdown_Utility.exe from the end of the action creates the prompt but only in a command window, not in the scheduled task.

Creating a shutdown/restart task without a user prompt works fine (not using ConfigMgr_Shutdown_Utility.exe)

Is this something you've seen with this function/exe? Can you shed any light on why it would be 'failing'?

Thanks for your help.

Steven

Server - 2008R2 SCCM 2012 SP1
Client - Windows 7 SP1
Powershell 3.0 server and client
↧
↧

New Post: Additional tools

June 12, 2014, 6:03 am
$
0
0
Hi mdeboer,

could you guide me hot to add your scripts to this CM12 tool?

thanks
↧

New Post: Access clients by shortname

July 3, 2014, 8:16 am
$
0
0
I think we have the same issue. Our clients have (due to a legacy domain) multiple domain suffixes. SCCM will store these in the "Resource Names" device property. When a device has a different suffix registered in SCCM than the primary DNS name it will fail to connect. By changing the code to do a DNS query it will allways use the right suffix when connecting to a device.

This is our solution:

Folder: C:\Program Files (x86)\Now Micro\Right Click Tools
Files:
  • Device - Change Cache Size.ps1
  • Device - Client Information.ps1
  • Device - Group Policy Update.ps1
  • Device - Ping.ps1
  • Device - Rerun Advertisement.ps1
  • Device - Running Processes.ps1
  • Device - Schedule Shutdown.ps1
  • Device - Shutdown Restart.ps1
  • Device - System Information.ps1
  • Device - Tools.ps1
Replace:
 #Region Get Computer Name
if ($ResourceID.Contains(".")) {$CompName = $ResourceID}
else {
    $strQuery = "Select ResourceID,ResourceNames from SMS_R_System where ResourceID='$ResourceID'"
    Get-WmiObject -Query $strQuery -Namespace $Namespace -ComputerName $Server | ForEach-Object {$CompName = $_.ResourceNames[0]}
}
#endregion
By:
#Region Get Computer Name
if ($ResourceID.Contains(".")) {$CompName = $ResourceID}
else {
    $strQuery = "Select ResourceID,Name from SMS_R_System where ResourceID='$ResourceID'"
    Get-WmiObject -Query $strQuery -Namespace $Namespace -ComputerName $Server | ForEach-Object {$CompName = [System.Net.Dns]::GetHostByName($_.Name).hostname}
}
#endregion
↧

New Post: Disabling update check feature

July 3, 2014, 8:57 am
$
0
0
We had to search a while to find this "hidden" feature.

You can disable the update check feature by editing a text file.

Folder:
C:\Program Files (x86)\Now Micro\Right Click Tools

File:
RCT-Options.ini

Change from true to false:
[InstallProperties]
PSExecLoc=
AutoUpdate=False
WOLPort=12287
WOLUnicast=False
PacketsToSend=2
Version=2.0
↧
Viewing all 140 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>