Duke5A

Try opening the Print Management snap-in, look under drivers, and bring up the properties for said driver. It should give you a list of every file it uses and where it is located. You can try adding these to the exclusion list.

We have a handful of 790s that I push Win7x64 out to via WDS. We really haven't had any issues. I use a 32 boot WIM to PXE boot from and just import the driver for the NIC into the WDS console. Is your WDS server running on Win2k8 R2? Only the Win2k8 R2 version of WDS version supports adding drivers at the console. If you're running an older version you have to export the boot WIM, mount it, jam the driver in, and import it back into the WDS server.

Do you have caching of SSL pages turned off for that user? Everything from OWA is delivered via SSL so the attachment may never be dumped to the cache directory to be opened.

I used this guide to get IPtables to route traffic between the NICs and forward port 80 to Squid. Linux: Setup a transparent proxy with Squid in three easy steps The only thing it doesn't cover is restoring the rules on reboot. IPtables will revert back to a stock configuration after every reboot unless you import the rules again. The answer to this is in post #13 of this thread. [ubuntu] Ubuntu v8.10 Auto Start IPTables - Page 2 - Ubuntu Forums I hope this helps...

We're in this boat too; Google DNS gets priority with our ISD provided DNS servers in the bottom of the list. It works great...

I just did this a couple months ago for a segregated guess WiFi VLAN. I setup Squid 3.0 as a transparent proxy and iptables to pass the traffic between NICs. Port 80 gets forwarded to Squid, a couple ports go straight through, and the rest get blocked. Once through, Squid will then forward the traffic up to the ISD for content filtering. The whole thing runs in a VM and even has a captive portal splash page for users to accept our terms of service. It works nicely, but as already noted, HTTPS doesn't forward through Squid.

I've got staff that needs to use an old version of Borland DB to access SIS records from an old system. The installer will through a fit and exit if you try and run it on a 64bit machine. So I packaged it into an MSI on a 32bit OS and ran the MSI on the 64bit machine to bypass the check in the original installer and it worked. I would imagine this process would work for other pieces of software if the need arises.

I don't know if netbooks would fulfill your needs, but we rely pretty heavily on Dell Latitude 2120s. 2GB ram, dual core atoms, six cell batteries, and a full rubberized exterior. They hold up remarkably well and are easy to service. They're small enough to get 30 into a cart too.

We're doing what you're looking to do with the exception that our wireless hardware is all Cisco and the above services are running on domain controllers. DHCP, Radius, CA, and DNS are all running on a DC inside of a VM. We haven't had any issues with them all coexisting on the same box and even have the second DC running the same services for redundancy. Defining the wireless network in GPO has even saved us a heck of a lot of time when imaging student netbooks in mass. I hope this helps...

He means, whatever you do, DON'T format it until you've exhausted all other possible options. There is a good possibility the controller in the external caddy has failed. Remove the drive like Dos_Box recommended, place it into a functioning machine (I wouldn't use another caddy for this), and retry your recovery efforts from there. Good luck.

DF probably just invokes something like wuauclt.exe /detectnow to install the updates, so it accomplishes the same thing as if the update schedule were configured in GPO. I wouldn't change anything if it works.

This will give you a detailed description of how NCSI works, and how to disable it. Windows 7 Network Awareness: How Windows knows it has an internet connection - Super User Blog

Your shares aren't sitting in a DFS namespace are they? Have checked the AV client on the storage server?

Are you using a proxy of any kind? I've seen proxies mess with Java applets and typically adding the offending sites to the proxy exemption list fixes it. Watch out though, Java will grab proxy settings from whatever the default browser is set to. So if you set you exemptions via GPO for IE, and a particular user has Firefox installed and set as default, Java will pull its proxy settings from Firefox.

We're a six site school district (not a boarding school, but just a regular public school) with about 4,000 students and the kids will use about 35GB a day, and staff will use 20GB. Squid might be a good option for you. I run two Squid proxy servers, one for staff and one for students. It'll do caching and you can block some of the more non-educational traffic intensive sites like Pandora and Vimeo for students while keeping it open for staff.

We use Deep Freeze and WSUS in our district and it actually works quite nicely. We setup a scheduled event in Deep Freeze that wakes all the systems at 1am and places them in maintenance mode for an hour, and the machines are set through Group Policy to install updates from the WSUS server during that hour. At the end of the maintenance cycle the machines will reboot frozen and shutdown.

Give this utility a try, it'll snoop for WOL packets so you can see if they're even getting through to the client. Depicus Wake on Lan Monitor/Sniffer Or just install a packet capturing utility of your choice and sift through the results. If it isn't working with machines that worked before though I would be questioning whether or not it's even making it through. Did the IP of the server change that you're using to send WOL out from, or were there any changes in the switching configuration? For WOL to jump subnets it requires configuration on the switches.

Some information is missing from the gpresult dump. The very first thing that should be displayed is the LDAP path to the computer object. It probably isn't shown because you ran it as a local admin. It should look something like this: COMPUTER SETTINGS ------------------ CN=Workstation01,OU=Computers Test,DC=TESTDOMAIN,DC=LOCAL Last time Group Policy was applied: 5/3/2012 at 9:39:51 AM Group Policy was applied from: DC01.TESTDOMAIN.LOCAL Group Policy slow link threshold: 500 kbps Domain Name: TESTDOMAIN Domain Type: Windows 2000 Applied Group Policy Objects ----------------------------- Computer WDS Staging Default Domain Policy Local Group Policy The computer is a part of the following security groups ------------------------------------------------------- BUILTIN\Administrators Everyone Debugger Users BUILTIN\Users NT AUTHORITY\NETWORK NT AUTHORITY\Authenticated Users This Organization Workstation01$ Domain Computers Wireless Computers See the LDAP path? It's the first thing listed under Computer Settings. This shows you where the computer object resides in Active Directory and right under that it'll show you what group policy objects have been applied. The reason this is missing is because you ran gpresult as a local admin and this account doesn't have the rights to query some of this information in AD. What you need to do is log onto the machine as a domain account that has local administrator access on the computer. Then you can drill down through the start menu to Start Menu\All Programs\Accessories\Command Prompt, right click it, and select Run as Administrator. Now when you run gpresult it'll give you everything. Hang in there, we'll figure this out.

Truer words have never been spoken. Unfortunately we're absolutely married to some really old crusty software. The funny thing is it'll run just find on an x64 system, but it's the installer that complains and won't finish. I've gotten around this by packaging it up into an MSI or Ghost AI on an x32 system and using the package on the x64 box. It's dirty, but it works for those oddball pieces of software that are used once in a century.

The DNS suffix lines up, but I don't see COMPUTER SETTINGS under the gpresult results. I think it has to be ran from an elevated command prompt to give those results.

We do something similar for student home folders. The folder structure kind of looks like this: Students 2020 Student A Student B Student C 2019 Student D Student E 2018 Student F Student G ...and so on The share path to a student's home folder would look like this: "\\BIG-NAS\Students$\2018\Student F" One hidden share that contains all graduation years for students, and under the graduation years are the AD names for each account. Share level permissions are granted full for everyone, and file level permissions are set for students and staff to only have modify permissions on the student's folder, and nothing further up the line. This prevents people from being able to crawl up the tree and enforcement is only done on the file level. Plus, only give students modify and not full. This will keep the little buggers from taking ownership and denying access to everyone else. If you have your students organized by graduation year in AD, then you can use this script with some minor editing to set their home folders for an entire grad year at a time. strHomeDrive = "H" strHomePath = "\\BIG-NAS\Students$\2020\" Set oContainer = GetObject("LDAP://OU=2020,OU=Students,OU=Your Users,DC=yourdomain,DC=com") oContainer.Filter = Array("user") For Each User in oContainer User.Put "homedrive", "H" User.Put "homedirectory", strHomePath & User.samaccountname User.SetInfo wscript.echo User.samaccountname Next

Run "gpresult /r" at the command line and verify the policy is even being applied. If it is, then run "RSOP.msc" and verify the setting is being applied. If it is, then check the DNS suffix of the network connection by running "ipconfig /all" at the command line. The way Windows Firewall determines the difference between a domain network and a public network is through the DNS suffix. If the suffix on the network connection matches the suffix it received from its last group policy update it'll use the domain profile settings on the firewall, and if not, it'll fallback to the standard profile. If it doesn't believe it is on the domain network then this could be a reason why it is ignoring your GPO settings.

I still prefer to use scripts myself. I've got a sub rolled into our VB logon script that deals with printers. Thus far it handles W2k/XP/7 without issues using a 2k8 32bit print server that has both x32 and x64 drivers loaded for every printer it hands out. Anything you can query through a VB script like computer/user LDAP path, group membership, machine name, AD site, everything in WMI, etc, can be used to set conditions for who gets what printer, and which is eventually set as default. For instance, we have our machine names and printer names done by building and room. So a printer in Neverland Elementary room 5 would be named NLE-RM05, while the machines would get named NLE-RM05-TW01/NLE-RM05-SW01. A couple lines of code in the script will hand out classroom printers for every building in the district to where they need to go by parsing the machine name and lining it up against the expected printer name. An added bonus is it'll even set the default printer. There are multiple ways to go about printer deployment. If all you're doing is pushing out a couple of copiers to every machine in a building, the Print Management would be the way to go, but if you get to the point where printer deployment starts to dictate how you setup your AD structure you might want to give scripting a look at.

Anything CS5 on up in the video editing suite of programs requires a 64bit OS; this will include Premier Pro and After Effects. System requirements | Adobe Premiere Pro We made the switch to 64bit last school year and haven't come up across any serious issues. What you really need to do though is build an x32 and x64 image and run them side by side with your software load out before making a definite decision.

I've been in this boat, and even if you write it into the plans that area A is supposed to be on at time X, and area B at time Y, it isn't going to happen. The work will get started, and you'll quickly learn a new dirty phrase, Change Order. Pack your people up and move them out of harms way. Trust me, it'll save you much grief.