ces973

Symantec just released Endpoint Protection 11.0.5 yesterday, which fully supports Windows 7. Earlier versions, I kept getting an incompatible driver error, and not all the modules worked.

Thanks. I had forgot R2 wasn't released yet. It's been on our Software Assurance site, and our software reseller has licenses available for purchase up on their website. Shouldn't be too much, if any difference between that and the public release, I would think. I cant move my domain to a 2008/R2 native level because I still have 2003 DC's. I do have a 2008 DC as well, so I wouldn't think I would have run the domainprep and forestprep again. Would like some more info on that, though. I also don't want to remove the server from production, and start again clean, if at all possible. Are you required to run the domain/forest prep if you already have a 2008 DC in production, or are you just adding a 2008 R2 server to a 2003 domain? I know I will have to do the adprep process again to update the schema. Also, my 2008 DC is not my Primary DC, I'm wondering if I should move all the FSMO roles over to it, make it the PDC, and then upgrade, or do it in reverse order.

I thought so, but I wasn't sure. All my 2008 servers are x64, so no worries in that department.

Anyone partake in a straight 2008 to R2 upgrade yet? I'm looking to upgrade my 2008 DC next week, and I was just wondering how much hassle I will be getting myself into. The server is a DC, but not the PDC, running DNS and DHCP. Since it's my only 2008 server, I will probably make it the PDC after the upgrade. I'm guessing I just get a backup of the system state, pop the disk in and run the upgrade? Will this then upgrade the AD schema, or do I have to do that manually?

Version 11 is Symantec Endpoint Protection, and that works fine on 7. Last I knew, Symantec dropped SAV CE for Endpoint Protection.

I just requested MAK keys until we get 25+ machines in. I have a KMS server up and running with our 7 KMS key, but there is no way we're going to have 25 Win7 machines in anytime soon.

The patch was released and it DOES accept Win7 KMS keys. Here is the x64 link... Download details: Update for Windows Server 2003 x64 Edition (KB968915)

You're right, this webcast is absolutely riveting. From what I've read, the update for 2003 servers with KMS 1.1 installed will be out August 11. So, I guess I will have to wait until then to activate my Win7 machine. Weird thing is, I have 3 days since installation, to activate it. I thought it was normally 30 days? These 5/25 minimums for activation are going to be a PITA, me thinks.

It's not in the "Windows" section on the download page. It's under the "Software Assurance" section, at least on mine. I was wondering why I had Vista Enterprise and no Win7 Enterprise as well.

It's on a 2003 SP2 x64 box. I tried to install it on a 2008 SP2 x64 server, and kept getting an "insufficient space" error, which kind of befuddled me. I wonder, how are you supposed to activate Win7 or 2008 R2, which isn't out yet, with KMS keys, if you're supposed to install KMS on one of those two systems?

Anyone having trouble activating their KMS key? I'm quite the KMS newbie, just set it up yesterday actually, and keep getting an invalid key error when I try to activate our KMS key with the MS Licensing Center. Do I need to get a MAK key, and activate that, or should the KMS key work? About the only thing I've done to the KMS server is run the installer and the KB update. I then tried to activate our KMS key, and nothing! So, any help would be appreciated.

Awesome! Downloading as I type this...

I had an issue with WSUS where all my SID's were the same from imaging machines, and looked like most of my machines weren't showing up on the server, but were still locked down by GP and getting updates. I used this in a batch file, and set it to run on logon, and most of my machines came back... @echo on net stop wuauserv REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow The latest version is 3.0SP1. There is SP2 out, but I think it's still in the beta/RC stage.

Are there any extra accounts on the PC? We had a student last year create a text file, rename it with a .bat extension, and then ran it. The file created a local admin account, to which the student logged into and deleted our admin accounts. Unfortunately, at the time I had all of our logon scrips as .bat files, so I couldn't block access to the command prompt.

From what I've read, .adm and .admx files are basically the same, the only difference being that .admx files are used by Vista/7 machines running RSAT, or Server 2008. They both have a .pol file extracted from them, which GPO uses for the policies. I read through the 1,000+ settings yesterday and have about got mine tweaked to where I want it. May need to make a few more changes though.

I've installed it on a few machines to test, but I'm waiting for my WU server to get it before I roll it out to everyone. That will give me time to play with the GPO settings.

I went from x64 7000 to x64 7100, and certain aspects seem slower to me, like booting up and longer load times after logging in.

Mine is a 4.3, only because I have a 8400GS as my video card, which actually got a higher score for gaming graphics, than it did for Aero graphics... go figure! Processor Intel® Core™ i7 CPU 920 @ 2.67GHz - 7.4 Memory (RAM) 4.00 GB - 7.4 Graphics NVIDIA GeForce 8400 GS - 4.3 Gaming graphics 2298 MB Total available graphics memory - 5.1 Primary hard disk 242GB Free (279GB Total) (2x 150GB VeliciRaptors in Raid-0) - 6.1

I'm also a big fan of the 6940's. We have plenty of them around our district. I also like the 6980's, or whatever the latest model is, because of the wireless capabilities for laptop carts.

I think, as long as you're covered for licenses, it really doesn't matter what you use for a key. We are looking to get around 250 MSI Wind's this summer, which all come with XP Home, so we are having to buy Vista Business licenses, then downgrade them to XP Pro. Which then, we will image them all with one key. I'm not sure if we had bought a volume XP license at one time, or not, though.

We have a director and 1.5 techs in our district. We have about 1800 students, 200 staff and about 1000 Windows PC's, all located in about 6 or 7 different buildings.

We had this happen with some 1022's. You have to go into the printer properties, go to the "ports" tab, and uncheck "enable printer spooling".

I had realized, a little too late, that you cannot set up a WPA-PSK via the wireless policy in the GPO. The reasoning is that the wireless GPO settings are supposed to be for a sizable enterprise-type setting, where the PSK is more for home/small office users. I'm probably looking into implementing a radius server in the future to deal with any future laptops we will be getting in our district.

I just wear a collared polo and khakis/Docker's. In the summer, when there are no teachers here, it's t-shirts and shorts!

Celeron 2.2GHz 512MB of shared RAM Intel integrated graphics, probably only had, at most, 32MB of RAM allocated to it. Ran decent, only slightly sluggish. Had Aero turned off, but nothing else. Worked for internet and office applications. Didn't have Office 2007 on it, only 2003, so that might have made a difference.