Blog Posts tagged with Windows 64-bit

Ask a question

Verify When Windows Password was Changed

In our environment our user account group creates accounts using Novell eDirectory.We currently sync from eDirectory to our domain, but not the other way.We sometimes run into an issue when a user changes their password using their machine instead of a link provided that changes it in eDirectory. This causes issues with other shared sites were passwords are not synced up.

I've seen tools that will do this, but were not supported in Win 7 x64. To assist in troubleshooting I created a powershell script that will prompt for user ID, and it will return when the password was last changed on our domain. This was created from a variety of different Google searches with a few modifications to meet our needs. I thought I would share just in case anyone else has a similar wacky environment.

$user = read-host "Enter User ID"
$searcher=New-Object DirectoryServices.DirectorySearcher
$changedtime = [datetime]::fromfiletime($results.properties.pwdlastset[0])
$c = "The user, $user has changed password last time at $changedtime"



After prompted for User ID this script will return a time stamp of when that password was last changed.

View comments (1)

Creating a Windows 7 sysprep image without having to install any drivers with post install tasks

With a windows 7 syspreped image I can found a method that has not failed yet.  I have only 2 admin images, one 32bit and one 64bit and one base 32bit academic image.  I discovered by placing any missing drivers I have to install post sysprep back on my master machine in the windows\inf structure that model computer will then find the driver by itself next time.

Under windows\inf I created on subdirectory called tmccdrivers and then created subdirectories for each model.  I put only the drivers I had post install in here to keep it's size down.  Under most of the models I have audio, video.  then some I need mei heci tpm.  I even have 10 models of laptops this works for.   currently my images suppport 18 pc/laptop models from gateway, dell, hp and lenovo.

When we get a new model staff deploy's a image to it.  They find the missing drivers and place them on a share named imagedrivers by model\type directories.  I have a midlevel task that copies this directory structure to c:\windows\inf\tmccdrivers.  They deploy the image again to that model and the drivers are found without me having to create a new master immediatly.  When I update the master (usually monthly) I move the drivers from the share to the master to save copy time during imaging.

Once I did have to copy the drivers for a video card from the temp folder vs the install folder, something to do with compressed files if I remember.

Because our master is hardware independant I now base all my images on software/licensing and they work in any classroom even if all the machines are not the same model.

View comments (7)

TeamViewer ID Custom Inventory Rule for K1000

We use TeamViewer a lot. It’s been extremely useful, but only when we can connect. Having KACE track the TeamViewer ID numbers will help keep up with changes. TeamViewer Manager is nicely made and easy to use, but it requires manual input and updates.  KACE is a good way to confirm the info in TeamViewer Manager if we run into trouble.

We had a custom inventory rule in KACE that checked the registry and returned the appropriate value. Then we updated the KACE Agent from 5.1 to 5.3 and it stopped working. The information being returned was useless. It wasn’t even readable. I called KACE and we tried several different variations of RegistryValueReturn, but never got it working again.

I came across a post asking about this exact issue and it got me thinking about it again. And I think I have a workaround.

1. Create a .bat file with the following script.

@Echo off

for /f "skip=2 tokens=3" %%A in ('reg query hklm\software\teamviewer\version7 /v clientid') do set /a var=%%A

echo %var%


2. Save the bat file to a network share.

3. Create a Custom Inventory Rule.

ShellCommandTextReturn ("\\Server\Share\TVID.bat")

This bat file only checks 32bit systems, so highlight the appropriate versions of Windows under Supported Operating Systems.

If TeamViewer is installed the rule will return the ID. If it’s not installed you get “ERROR: The system was unable to find the specified registry key or value”. So far it’s working on Windows XP and 7.

Script for 64bit.

@Echo off

for /f "skip=2 tokens=3" %%A in ('reg query hklm\software\wow6432node\teamviewer\version7 /v clientid') do set /a var=%%A

echo %var%

View comments (5)

Custom Inventory Rule and Accessing Registry on 64 Bit OS

Dell Kace agent is a 32 bit application. Hence on a 64 Bit OS, registry path HKLM in Dell Kace agent will point to HKLM\Software\Wow6432.

Hence, In Custom Inventory Rule, to access HKLM\Software of the 64 bit hive, use HKLM64\Software.


On a 64 Bit OS, to check the existence of a registry key from HKLM\Software\Intel construct Custom Inventory Rule as

Be the first to comment

PowerShell Script Execution Disabled

By default, PowerShell will not run script files. This is considered a security feature to help one from accidentally running a PowerShell script.

The error will look something like:  “File <path>\<file> cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.”

There are a few policy settings available:

  • Restricted – this is the default, it does not load configuration files or run scripts.
  • AllSigned – this setting requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer.
  • RemoteSigned – this is the setting typically recommended if you are going to be working with scripts. It requires that all scripts and configuration files downloaded from the Internet be signed by a trusted publisher, but those created locally do not need to be signed.
  • Unrestricted – as you might expect, this setting loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the Internet, it will still prompt you for permission before it runs.
  • Bypass – if you really want to shut this up and are not concerned about security, this setting blocks nothing and suppresses all warnings and prompts.

First, to change the policy you must have rights to do so. Right click on the PowerShell shortcut and choose “Run As Administrator”. Then, you’ll be able to change the script execution policy directly by typing: 

Set-ExecutionPolicy RemoteSigned

You’ll get the warning, “The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution?” 

If you skipped the part about ensuring the console is run as administrator, you’ll be stopped here with a security failure with the message, “Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied.”

The policy exists separately for both the 32 and 64 bit instance of PowerShell on your system. If you are running PowerShell via a 32-bit application, like the Admin Script Editor, be sure you set your script execution policy in the 32-bit instance of the PowerShell console.  If you look, you’ll find shortcuts for “Windows PowerShell” and “Windows PowerShell (x86)” this second one represents the 32-bit version of the console.

If you are using the Admin Script Editor, it actually provides an option in its program settings to change the PowerShell script execution policy. Just click on Tools, choose “Options” and navigate to Script > Security.

Be the first to comment
Showing 1 - 5 of 7 results

Top Contributors

Talk About Mac OS X