I can only assume a user fed paper through one of our copiers with staples or paper clips still attached.
Friday, November 20, 2009
ID10T error with a copier
You might want to post a message with these pictures above copiers for users to see....
I can only assume a user fed paper through one of our copiers with staples or paper clips still attached.
I can only assume a user fed paper through one of our copiers with staples or paper clips still attached.
Enabling Remote Desktop remotely
So I ran into the need to enable remote desktop on a computer about 300 miles away this morning. Here is what I did.
First off I logged into my virtual XP machine with a domain admin account. I then launched the registry editor and connected to the registry of the remote machine. I then navigated to the following path on the remote registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
Once in the terminal server key, change the DWORD value for fDenyTSConnections from 1 to 0. (1 = Disabled, 0 = Enabled)
The remote machine won't automatically start working, so you'll need to reboot it. You can do this by running the following from command prompt.
shutdown -m \\remotecontroller -r
Enjoy
First off I logged into my virtual XP machine with a domain admin account. I then launched the registry editor and connected to the registry of the remote machine. I then navigated to the following path on the remote registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
Once in the terminal server key, change the DWORD value for fDenyTSConnections from 1 to 0. (1 = Disabled, 0 = Enabled)
The remote machine won't automatically start working, so you'll need to reboot it. You can do this by running the following from command prompt.
shutdown -m \\remotecontroller -r
Enjoy
Labels:
Enable,
Reboot computer,
Remote Desktop,
Remotely
Monday, November 2, 2009
Deploying Adobe Reader with ConfigMgr
So in my opinion Adobe makes it way to difficult to deploy Adobe Reader. The last time that I had to mess with this was months ago so I nearly forgot everything I needed to do to make my new Adobe package.
I started out with the need to deploy Adobe Reader 9.2 to workstations that had versions 9, 9.1, and 9.1.2. I downloaded Adobe Reader 9.2 from Adobe.com and ended up with an executable. Normally you can use a program like WinRAR to extract that contents of the executable, but not with Adobe executable's. Instead you have to use a switch.
You'll have to go to start, run, put in the location of the items, then the executable and tag onto the end of it -nos_ne. ( C:\AdbeRdr92.exe -nos_ne) When the Adobe window pops up you click Next, then when it's done you'll find you source files in the temp directory. Just don't get fooled by the modify dates. The Setup folder will have the current date and time stamp on it, but all the source files inside will have old dates. At that point you can use the Adobe Customization Wizard on the msi and distribute Reader throughout our organization.
Of course if you don't care to customize the installation you can just use the /sAll switch on the original executable. I choose to customize the installation so that the end user doesn't get prompted for updates or have to agree to the eula the first time it's launched.
Enjoy
I started out with the need to deploy Adobe Reader 9.2 to workstations that had versions 9, 9.1, and 9.1.2. I downloaded Adobe Reader 9.2 from Adobe.com and ended up with an executable. Normally you can use a program like WinRAR to extract that contents of the executable, but not with Adobe executable's. Instead you have to use a switch.
You'll have to go to start, run, put in the location of the items, then the executable and tag onto the end of it -nos_ne. ( C:\AdbeRdr92.exe -nos_ne) When the Adobe window pops up you click Next, then when it's done you'll find you source files in the temp directory. Just don't get fooled by the modify dates. The Setup folder will have the current date and time stamp on it, but all the source files inside will have old dates. At that point you can use the Adobe Customization Wizard on the msi and distribute Reader throughout our organization.
Of course if you don't care to customize the installation you can just use the /sAll switch on the original executable. I choose to customize the installation so that the end user doesn't get prompted for updates or have to agree to the eula the first time it's launched.
Enjoy
Labels:
Adobe,
Adobe Reader,
ConfigMgr,
Reader,
SCCM
Subscribe to:
Comments (Atom)
