I will test this at work sometime this week and update. Thanks again for your help. With the holidays, I haven't been able to do a whole lot with this.
I'm very limited in the freedom I have on the Domain Controllers. The script is not going to be implemented via login, but rather as we deploy the new machines to the users. I'm just going to make it a task of the team setting up the new 2k workstations to double-click on the vbs file to install...
Here's a look at some of what I have, but I don't want to determine the OU. I want to determine the Department!
'Determining OU Name
Set objSysInfo = CreateObject("ADSystemInfo")
UserADsPath = objSysInfo.UserName
arrTemp = split(UserADsPath,",")
OUName = arrTemp(1)...
I have very minimal vbscript knowledge, and I was asked to come up with a script that will retrieve the user's Department in AD, and assign network printers accordingly. Our AD isn't structured well, and all users sit in the USER container and are not separated by OUs. Any help would be great!
Remedy is a great product with great support. It's used in our environment and interfaces wonderfully with Exchange and our paging system. Recommended.
Even with Ghost or other imaging software, there are minor tasks required for setup. If you use Ghost and Sysprep combined, you can eliminate most of the driver setup, but you're still required to enter the computer name on startup. If you are going to use the image route (Ghost and Sysprep)...
depending on the BIOS manufacturer, you normally update or flash the BIOS from a floppy. Some manufacturers have utilities that allow you to update the BIOS from within the operating system. Either way, you'll need to put the old processor back in to at least be able to boot to floppy or OS.
You might also try changing the Language Level in Adobe before printing. I think the default is two. We have a document at work that will only print in level 3. The setting is under postscript options...
We were running nt 4.0 sp 4. The PC had MouseWare NT installed, but also had IBMs Netfinity installed. There were to Devices (control panel...devices) starting as System devices - MouEX and Mouse Class Driver. By removing MouseWare NT, this allowed only one device driver to control the mouse...
Martin,
If you can point me in the direction of those calculators, it would be much appreciated. 185 watts should be plenty of power for the average desktop, but we're adding high end graphics cards, usb wireless mice, and gig NIC cards to a few select machines. These are critical machines...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.