Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Locked thread
Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

Sock on a Fish posted:

So, I'm going to be deploying a domain controller at that remote office soon. Are there any drawbacks to just letting it operate as a domain controller for our current domain, or should it get its own domain in the forest?
I went through this back in May and I didn't set up a different domain. My situation might be different because we use SBS, and I probably couldn't create a new domain if I wanted to but this other office is a state away and only has 6 employees. I set up the domain controller over there and set up an IPSec VPN tunnel between the two sites.

Then I went into Active Directory Sites and Services to define a new site and made sure to set it up so that it knows that other domain controller is at the other site. This helps it conserve some bandwidth, so it's not treating it like it's on a LAN.

This is also about the time I started using DFS with replication which really helped, since there's now no direct opening of files across the VPN (automatically accessed the local copy and replicates later).

So yeah, after this experience, for us, I don't think I would create another domain even if that office was bigger.

Adbot
ADBOT LOVES YOU

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
I'm so glad this thread hasn't died.

I would like get some discussion going on the special configuration needs for mobile/laptop users. Right now, I'm struggling with how to manage some of these systems. We've got techs who might never come into the office for a month or more, because they go directly to jobs from home, and go right back home afterward.

Since they aren't connected to the domain for long stretches of time they don't get group policy changes, software updates, etc. I am working on a way for them to get virus updates with NOD32 without them having to connect to he VPN, but it isn't fleshed out yet (I know you can have NOD32 mobile users update directly from the internet, but I'm trying to avoid that just to avoid embedding our credentials on portable computers).

I'd love to hear how some other administrators handle issues unique to mobile users.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

BangersInMyKnickers posted:

Ideally you would want to make a WMI filter that only applies if it does not see the Symantec Antivirus program installed on a system. Unfortunately at this point we hit a limitation with WMI filters that makes life difficult: WMI filters cannot be used to detect the absence of something and return a true value to the filter falls within scope. For this kind of thing you will need to revert to a batch script that runs a reg query that looks for the indicator key and then catch the error level and execute the rest of the batch file from there, either by doing file manipulation, registry merges, or msiexec commands. Hopefully in future iteration of group policy you can customize a WMI filter to fall within scope on your choice of a true or false return instead of just true, but at this point the flexibility isn't there.
Here's how I got around this just recently.

Why I needed a negative result:

We have typically been using Office 2003 Basic edition on our computers. This is Outlook, Word, and Excel. More people need to view Powerpoint presentations than need to create them, so I had the (free) PowerPoint Viewer 2007 being pushed out to everyone. I also had the Office 2007 Compatibility Pack being pushed out to everyone, which allows them to view Office 2007 files in Office 2003.

We don't do upgrades here all at one time. What happens is that basically someone's needs change and their existing old machine can't do what they need to do effectively anymore, so our upgrades are piecemeal. As I get new machines, I get Office 2007 for them. On a recent one I noticed that Windows update had service packs for the compatibility pack and the viewer (which were both installed despite Office 2007 Standard, which includes Powerpoint, being installed). Now I wouldn't have cared since it didn't negatively affect things, even though it was redundant, but for some reason the service packs wouldn't install, and so it was always prompting for updates.

I wanted a way to have group policy NOT install these components if they weren't necessary. The compatibility pack shouldn't be installed if Office 2007 is installed (in my case, this means if Word 2007 and Excel 2007 are installed) and the Powerpoint viewer shouldn't be installed if Powerpoint 2007 is installed (but it should be installed if Office 2007 Basic was installed, or any other non-Powerpoint 2007 parts of office).

The solution:

I created a policy called NegativeValues. This policy will assign values on the machine that I can then check for in WMI filters for installing software. I'm not using a separate policy for each value because I am not using a WMI filter on the policy itself, I'm using item-level filtering within the policy.

Originally I was setting registry values, but then I found out that querying the registry through WMI is a pain in the rear end, so now I'm setting environment variables instead.

Computer Configuration -> Preferences -> Windows Settings -> Environment

These are easily queryable from WMI and don't take forever to process. I use the Replace action so that if the result of the item level targeting changes, the variable will be deleted (in theory; I have not tested this). I have it creating environment variables named NegativeValues_whatever but the name doesn't matter since you need to specify it in your WMI filter. You might want to make it something you and your other admins will recognize if you happen to be looking in the environment variables on any given system. The value doesn't matter because you're only really going to be checking for its existence. I just used 1.

On the common tab, you'll see a check box for item level targeting. Check that, click the targeting button, and then new item. Your choices here are a lot better than you can do with WMI alone, in my opinion, especially since you can use [multiple] WMI queries here if you want. In addition, you can negate any of these by changing it to IS NOT in the item options.

For my purposes, I did come up with a WMI query that could tell if an individual office component was installed, but it took about 10 minutes to run with the CPU maxed on a newer dual core machine (only uses one core though), so it really wasn't viable. I found it a lot to easier to just check for the existence (actually the lack of, using IS NOT) of the registry keys (HKLM\Software\Microsoft\Office\12\[Word|Excel|Powerpoint]) and it runs really fast.

Then I created a WMI filter, like Powerpoint2007Missing which consists of the following query:
code:
SELECT * FROM Win32_Environment WHERE Name = 'NegativeValues_Powerpoint2007'
and I apply that to the policy that installs Powerpoint Viewer 2007.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
Is anyone having a problem with drive maps in Vista? I have a few Vista machines here where the drive mapping policy is not working. It works on all of the XP machines, it works on some of the Vista machines, but not others. It works on my machine, but I don't think it's a problem of access rights because when I log onto to one of the affected machines with my credentials, it still doesn't work.

The odd thing is, I've looked through the event log and I can't find any errors. I've run the results and I see no problems; as far as I can the policy is definitely being applied, but I have no errors at all. I'm stumped.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

Mierdaan posted:

Are you using the new Vista/Server2008 Group Policy Preference Objects, or old-school logon scripts? If the former, and the Vista computers have UAC turned on, you'll need to follow this KB to make it work.
I am using the preference object, UAC is on, and I've tried that solution. On my machine, UAC is turned on, but the registry entry doesn't exist and the policy works fine. On the other machines, UAC is turned on, and I tried to add that registry entry and it made no difference; still doesn't work.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

Mierdaan posted:

Same behavior for all users? Does local admin vs not make any difference?
My user is a domain admin (domain admins by default are in local admins) and it seems not to make any difference. I haven't tried logging on a normal domain user to my workstation, but my user logging in to an affected one doesn't make any difference. I found out my printer preferences stopped working altogether, and I had them in the same policy as the drive settings so I separated them out but it too made no difference.

Here's some new info: the other machine I thought was affected is a laptop, and I just realized he wasn't on a wire. When I had him reboot connected via wire it worked fine.

So I think at the moment I'm down to this one machine. It's brand new (refurbed, but a new installation). I even took it off the domain and put it back on. I've tried gpupdate, both /force and /sync (over and over).

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
The laptop turned out not to be affected. The one that is is a desktop and is wired only; sorry for the confusion.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

pyrotherm posted:

Does anyone here know if you can install RSAT on Windows7 RC?

I have been trying to do this, and have even downloaded the RSAT tool for Windows 7 from Microsoft's website:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d#filelist

All that this does, is give me an error stating: "This update is not applicable to your computer"

Any help with this would be greatly appreciated!

quote:

Remote Server Administration Tools for Windows 7 can be installed on computers that are running the Enterprise, Professional, or Ultimate editions of Windows 7.
I haven't used Win 7 RC yet so I don't know what it entails, but if it doesn't report as one of the above versions that's probably the reason.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

IT Guy posted:

gently caress, another issue. We have some software that updates daily for a user and doesn't work unless the user is a local admin. Trying to cut this poo poo out because users are downloading spyware/malware. What is my best way to get the software working without a local admin?
I haven't used this a lot yet, but it has been working well so far:

http://www.scriptlogic.com/products/privilegeauthority/

I don't like things like this, but I needed it for our shipping department. I just gave her a new machine with Windows 7, and installed the latest UPS software, and the drat thing wants to update every other day (not really an exaggeration), which needed admin privileges. I used this so that only the updater application will run with the admin privileges and it has worked great since.

Right now it's based on path or file name, which is obviously subject to abuse if the application in a location that is writable by the user, but they're looking into a hash option.

The only other thing I don't like about this is that is somehow uses group policy, but it applies its own settings to a GPO which are not viewable in Group Policy Management, they are only viewable in their own application. It's a bit weird.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
Authenticated Users is basically any user at all. The difference between Authenticated Users and Everyone is that Everyone includes stuff like the "null user" that can be used to query things across the network. There is probably a little more to it, so yes you should google it, but I think it's basically a slightly more secure "Everyone."

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
I'm having a problem with software installation via GPO that I can't nail down. The software in question is NSClient++ (Nagios monitoring agent for Windows). It already comes as an MSI.

The MSI installs just fine via the GPO. The MSI updates an existing older version of the software just fine via GPO.

The problem occurs when I manually uninstall the software. What I've seen in the past on other software deployments is that in this case, the software will just be reinstalled on the next reboot.

What's happening here is that the reinstall is attempted but quickly fails. There are no error messages in the event log, the application doesn't show up in Programs in control panel, the files and service are not created. For all intents and purposes, the install didn't happen, EXCEPT that it does show up in the MSI cleanup tool. It doesn't show up in there after the manual reinstall was done, only after a reboot when it attempts to reinstall it.

Removing that entry from the tool does NOT allow it to be successfully reinstalled via GPO.

I am at a loss.

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy

Docjowles posted:

Try turning on verbose logging for the installer service. Can be done via registry edit or group policy. This has helped me in the past finding problems with Java's abortion of an installer :mad: KB article.
Actually, I forgot to mention it, but I did this, and no log file was created. I checked the value of the %temp% variable for both my user (it shouldn't be here) and for the system environment variable (C:\Windows\Temp). I even started by clearing those directories so that I could more easily see a new file.

I've done this on two different servers now, and no log was created during the installation via GPO; even starting from scratch where there was no installation and uninstallation (that is, the install via GPO was successful, and still no log).

I also started a command prompt as the computer account using psexec -s cmd and ran the installer with msiexec (this time, specifying logging options via command line). This was successful for some reason. The log was created and showed no problems, the install worked well.

Adbot
ADBOT LOVES YOU

Briantist
Dec 5, 2003

The Professor does not approve of your post.
Lipstick Apathy
Okay I figured out what the problem was with logging. The KB articles say that you can use a value of "*" but it turns out that doesn't work! Setting it to "voicewarmup" does though. This is the result of one of my failed reinstallations:

quote:


=== Verbose logging started: 3/26/2012 15:03:29 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\svchost.exe ===
MSI (c) (28:E4) [15:03:29:453]: User policy value 'DisableRollback' is 0
MSI (c) (28:E4) [15:03:29:453]: Machine policy value 'DisableRollback' is 0
MSI (c) (28:E4) [15:03:29:515]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (c) (28:E4) [15:03:29:531]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1081574870,LangId=1033,Platform=589824,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (28:E4) [15:03:29:531]: Executing op: ProductInfo(ProductKey={76AAFD9B-9388-45D8-B464-217A69EDE358},ProductName=NSClient++ (x64),PackageName=NSClient++-0.3.9-x64.msi,Language=1033,Version=196617,Assignment=1,ObsoleteArg=0,ProductIcon=nsclient.exe,,PackageCode={0DA4D155-5ACC-4D01-AE99-6380B8F8785C},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (c) (28:E4) [15:03:29:531]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (c) (28:E4) [15:03:29:531]: Executing op: DialogInfo(Type=1,Argument=NSClient++ (x64))
MSI (c) (28:E4) [15:03:29:531]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (c) (28:E4) [15:03:29:531]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (c) (28:E4) [15:03:29:562]: Executing op: IconCreate(Icon=nsclient.exe,Data=BinaryData)
MSI (c) (28:E4) [15:03:29:640]: Executing op: IconCreate(Icon=nstray.exe,Data=BinaryData)
MSI (c) (28:E4) [15:03:29:640]: Executing op: IconCreate(Icon=doc.ico,Data=BinaryData)
MSI (c) (28:E4) [15:03:29:640]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing Product Features,Template=Feature: [1])
MSI (c) (28:E4) [15:03:29:640]: Executing op: FeaturePublish(Feature=Documentation,Parent=ProductFeature,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=Plugins,Parent=ProductFeature,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=ServiceRegistration,Parent=ProductFeature,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=MainProgram,Parent=ProductFeature,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=ProductFeature,,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=FireWallException,Parent=ProductFeature,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=CheckPlugins,Parent=Plugins,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=NRPEPlugins,Parent=Plugins,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=NSCPlugins,Parent=Plugins,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=NSCAPlugin,Parent=Plugins,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: FeaturePublish(Feature=SampleScripts,Parent=Plugins,Absent=0,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (c) (28:E4) [15:03:29:671]: Executing op: CleanupConfigData()
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\B9DFAA6788398D544B4612A796DE3E85\Patches 3: 2
MSI (c) (28:E4) [15:03:29:687]: Executing op: ProductPublish(PackageKey={0DA4D155-5ACC-4D01-AE99-6380B8F8785C})
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85 3: 2
MSI (c) (28:E4) [15:03:29:687]: Executing op: UpgradeCodePublish(UpgradeCode={0B36E3B7-0042-452D-B376-57E0C07ADDAA})
MSI (c) (28:E4) [15:03:29:703]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
MSI (c) (28:E4) [15:03:29:703]: Note: 1: 1402 2: UNKNOWN\Installer\Products\B9DFAA6788398D544B4612A796DE3E85\SourceList 3: 2
MSI (c) (28:E4) [15:03:29:703]: Executing op: ProductPublishClient(,,)
MSI (c) (28:E4) [15:03:29:703]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (c) (28:E4) [15:03:29:812]: Note: 1: 2318 2:
MSI (c) (28:E4) [15:03:29:812]: DoAdvertiseScript is returning: 0
=== Verbose logging stopped: 3/26/2012 15:03:29 ===
Unfortunately I don't really understand what's going on here. Any help is appreciated.

  • Locked thread