Peter33

Configure the system discovery, in the options tab, to only discover clients that have logged on to domain for ... chose how many days you like ...

That's a SQL query. You can run it from SQL Management Studio.

SELECT v_R_System.Netbios_Name0, v_GS_COMPUTER_SYSTEM.NumberOfProcessors0, v_GS_PROCESSOR.NumberOfCores0, v_GS_PROCESSOR.NumberOfLogicalProcessors0, v_GS_OPERATING_SYSTEM.Caption0 AS Expr1 FROM v_R_System INNER JOIN v_GS_PROCESSOR ON v_R_System.ResourceID = v_GS_PROCESSOR.ResourceID INNER JOIN v_GS_OPERATING_SYSTEM ON v_R_System.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID INNER JOIN v_GS_COMPUTER_SYSTEM ON v_R_System.ResourceID = v_GS_COMPUTER_SYSTEM.ResourceID WHERE (v_R_System.Is_Virtual_Machine0 = 0) AND (v_GS_OPERATING_SYSTEM.Caption0 LIKE N'%server%') GROUP BY v_R_System.Netbios_Name0, v_GS_COMPUTER_SYSTEM.NumberOfProcessors0, v_GS_PROCESSOR.NumberOfCores0, v_GS_PROCESSOR.NumberOfLogicalProcessors0, v_GS_OPERATING_SYSTEM.Caption0 This should work.

Just create an MST file (with Admin Studio or even Orca) to remove the file and the links druring the Installation. If the components are indexed in the msi and the other links are advertised, the msi will be repaired with every program start and the items will be back. This will also spare you the additional application. It's just unnecessary overhead.

Hard to tell. The Attribute should have self-rw rights for the owner and deny for everyone else. So if someone can read the value who is not supposed to, you have bigger problems already. First i would try to find out if NIS or NFS are enabled in your Environment, if yes then why and if it's really needed anymore. Could been a workaround for migrating data from UNIX to Windows or something like that. If there is no need, disable it. One thing less to care about.

This value is not used for several other connection methods, like NIS(Identity Management for Unix Systems), NFS(Network File System), OPENLDAP. Check your Domain Controller role Services. Maybe one of them is activated. This is also used for Google Apps (single signon). Second thought: This might be also a workaround for a self scripted single signon solution to some internet web service, without storing the password in the script. Your best shot si to inspect the machines of these users for login/autostart scripts.

Hi Peter, thanks for sharing. Unfortunately the script is not returning the "true" collection memberships for the client. Exclusions are obviously not saved in SMS_FullCollectionMembership. OK, Forget about the last line Just thanks for your work. Someone just deleted my Test-Clients exclusion collection.

Just to to make sure. Is the update group of your ADR holding a valid definition file? I remember a similar situation in our environment, when the upstream WSUS ran out of disk space and could not download the newest definitions anymore.

Try you push the definition update from the SCCM Management Console to your client and then check the client logs. Sort the directory by date to see which logs have any changes. Also check your windowsupdate.log for Errors.

Maybe a side effect of the ApplyGPOPack step?

We had the same problem and i was able to solve it with the help of 2 powershell scrtipts found on the net. Here is #1 to run http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69 It's pretty much selfexplaining and well documented. Here is #2 which has to be executed on every distribution point http://sccmroad.wordpress.com/2014/03/11/powershell-script-to-compare-dp-packages-with-wmi/ I had to modify it slightly though to get it working by removing "| Where-Object { $_.SideIndicator -eq “” }" from it. Only put 1 of the last 2 foreach-Loops to the script at a time and run them both ony by one.

Stop deploying it to the machine or disable the notifications in the deployment.

Thanks for link, Jörgen. Just downloaded the toolkit, played around with it for some time and adopted it. It's awsome and adding a new quality to application deployments.

Probably a silly question, but did you run a "use toolkit package" step before calling ztibackup?

OSD.zip No Problem. Here you go.

I doubt that this bug extends to UDI applications, because it would make no sense. The task sequnce itself holds no Information about these applications, because they get injected by a variable, which gets filled by a 3rd party product (MDT). The UDI applications are only listed in the XML configuration file in your OSD Settings package. No chance that the client can read them. So it should be safe if you don't use the install apllication step with the list of applications option. If you check your client logs (ciagent, ciadownload .. etc) you will see that every single policy for every step of the optional task sequence will be compiled. If a superseeded application is part of this task sequnce it will trigger some sort of backdoor Installation, even if the superseeding application itself is not deployed to the client. Pretty annoying. This caught me off guard 2 times before i figured out what's going on.

I would not use Configuration Items to set a user Wallpaper. Rather solve this with a Group Policy. http://deployhappiness.com/setting-the-desktop-wallpaper-background-with-group-policy/

Dependencies can only handle the install command of an deployment type. If you want to use the uninstall command you have to use the Supersedence of the application. You have to be careful though. There is also a bug while using supersedence for an application which is used in any optional task sequnce. The superceding application will be deployed to every machine which is targeted by the task sequence.

Thanks for the info, Niall. I was wondering which update was messing with our Windows 7 OSD this week. Is Microsoft aware of the problem already?

Check out the dependencies tab in the deployment type.

You may have to uninstall KB2837643. Check out this post http://helpdesk.missouristate.edu/two-microsoft-updates-cause-problems-with-outlook-2013/

Make sure that you define the correct update sources in the antimalware policies of your SCCM client. Also make sure that Windows update service "wuauserv" can conect to the internet via TCP 80/443 (Firewall rule for non domain profiles).

<![LOG[++++++ App enforcement completed (19 seconds) for App DT "11 g" Well, you can't expect the file to be present after 19 seconds. Best way to deploy the client is to create a Batch file and call the setup from there. Also put the response file in the source directory. pushd %~dp0 start /wait setup.exe -silent -nowelcome -nowait -responseFile "%~dp0NetListner.rsp" popd Edit: OK, i just checked our current command line this should do the trick pushd %~dp0 setup.exe -silent -nowelcome -responseFile "%~dp0NetListner.rsp" -force -waitforcompletion -nowait -noconsole popd

Depends on how you are installing the IE. Are you using wusa.exe? If yes the switch would be /log:"path+filename".

I have tried to solve this in our HTA. Unfortunately the GETOU Routine is to slow in a forest with several hundred OUs. It's sitting there for like 5 minutes to return the OUs. So what i did was using the GETADSITES function. Our Client OUs have the same Syntax in the AD sites. So i was able to create the OUs by adding the AD site to predefined Client OUs in a simple loop and feed them to the drop down list. Based on the Clients Default Gateway and Hardware type (Laptop/Desktop) the correct locations OU will be preselected in the drop down box.