Jedis

The only way I could include a network drive in the My Docs library was to have it sync the files offline first...

Hello, We are having an intermittant sync problem with several users. Basically, on the SAN, every user has a personal folder that they can save their files. First off, we map their network drive and then choose the option to "Always Available Offline" - and wait for the files to sync and be indexed. Then, I add the network share to the My Documents library and removed the existing My Docs and Public Docs entries from the library list. This works fine for 99% of my users. However, some of them have become desynced. I have someone who has 3 laptops - all three of them are having sync issues with the server. Files edited on one laptop are not being synced back to the network drive. Therefore, he has different versions of files across all three devices. What would have caused this to happen and how can I correct it without data loss? When the laptops are out of the office, they do need to be connected to the VPN in order to access the files on the network drive. He tells me he always connect to the VPN. If this is the case, why aren't the files syncing? Is there a better way to set this up than we have it now? How do I stop this from happening in the future? Any help is greatly appreciated! I am at a loss of what to do, short of gathering the contents from each laptop and going through each file one by one, looking for the files with the latest version.

http://ftp.dell.com/Printer/3130cn_PS_DRV_ENG_04-02-09-06_04-02-09-06.exe

We just installed this very printer on nine Windows 7 32bit machines this morning. The file you want is on Dell's website and has x86 and x64 drivers. It is called 3130cn_PS_DRV_ENG_04-02-09-06_04-02-09-06.exe and the drivers are in 3130cn_PS_DRV_ENG_04-02-09-06_04-02-09-06\English\Drivers\Win_x86 Hope this helps.

It's in the same domain. The 2003 server is in an OU under the domain running on the 2008 server. It can pull and see users from the 2008 server, but for whatever reason, local groups are setup on the 2003 server that grants access to shares running locally on that machine. This is why I am confused... logons to machines are processed by the 2008 server, but when I added a logon script to run on the 2008 server, it did not run on machines in that dept - hence why I think it needs to run on the 2003 server? Sorry, I don't know all of the technical terminology yet. Learning that this semester in my Network Mgmt class Unfortunately, there is no one around here to ask.

Hello, The main campus server is Windows Server 2008 R2 and acts as the main AD server. In a department, we have a Windows Server 2003 machine that has it's own AD groups that faculty and staff are added to. I tried creating a logon script on the 2008 server, but it does not run. How do I setup a logon script to run on the 2003 server so that people will automatically get their shared drives? Right now we are mapping them all by hand. Is there a way to get the two servers to work together?

We have some old OU's from 2005 that are named by the printer name and then AD group membership is assigned to the printers. But, these scripts don't work. Could you kindly point me in the direction of how to setup a printer server? We do not have access to the university servers to set this up and do not run any server OSes in our departments. Here's an example of the old scripts from 2005 that are no longer in use. We've since transitioned from XP to 7 so I am not sure if these will still work. These scripts also do not install the drivers... ' Usage:' prnport [-adlgt?] [-r port] [-s server] [-u user name] [-w password] ' [-o raw|lpr] [-h host address] [-q queue] [-n number] ' [-me | -md ] [-i SNMP index] [-y community] [-2e | -2d]" cscript c:\windows\system32\prnport.vbs -a -r IP_192.168.1.10 -h 192.168.1.10 -o raw -n 9100 cscript c:\windows\system32\prnmngr.vbs -a -p "Test Printing" -m "Test printer" -r IP_192.168.1.10 cscript c:\windows\system32\prnmngr.vbs -t -p "Test Printing"

Hello, I work at a university where all of the computers are on the same domain. Each department has their own OU in AD, where the technicians have access to create groups, computers, and to modify policies. Right now, after imaging a new computer, we manually install print drivers on each machine individually, depending on where the machine is going. We use Konica Minolta copy machines and these machines are setup to use Account Track codes, to track printing and to ensure only authorized users can print to the printers. We also have many "local" printers that are connected via ethernet and are assigned an IP address on the campus network. What I am looking to accomplish is some kind of way to automate installing printers and drivers, depending upon where the machine is going. We have the issue with the Konica copiers that the Account Track codes are stored on a per-user basis, so have not found a way to automate setting these up. We currently have to visit the computer in-person when the local user will be there, and have them login to the machine so we can insert the correct print code. If the machine is in a shared location, this code needs to be entered once for every user that signs into the machine. Obviously, there has to be a better way to do this. We do not have any kind of print server setup, as we do not have full control over the domain, just our OU's for the various departments we support. Can anyone offer any suggestions to better automate this for us? A sample script for adding printers depending on AD group membership would be great. And if anyone has experience with the Account Track codes for Konica Minolta machines, that assistance would be a god send! My goal is to make printers as easy to manage as possible -- ideally, when a user first signs into a machine, the logon script that maps their shared drives could also check their AD group membership and then install the print drivers and set the default printer, and any Account Track codes that were needed. Thanks in advance for any assistance you can provide! I am familar with AD basics, such as a logon script, adding groups and users to groups, and adding computers. I've looked into Group Policy Management a bit but haven't explored too much because I don't want to break things in a production environment. Please keep this in mind when replying with instructions