Jump to content


Kevin79

Established Members
  • Posts

    511
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Kevin79

  1. I must be missing something then. I added a computer to an AD group and it was added. I then remove it and it isn't removed from the collection. I did this close to two weeks ago.
  2. How would I create a collection that will check for certain software in the add/remove programs and it if exists, EXCLUDE it from the collection? I see ways of including computers in collection that have certain software installed, but not exclude them.
  3. Thanks. I'll look at those queries. With the wrapper, would it still give go information as to the status of the install? I.E. if it failed, why it failed.
  4. Two new questions: -I'm still having issues with it updating quickly. Can someone tell me what changes I need to make to do this? -After I run this query for the collection, how do I have it update the collection when a computer is removed? I.E. I have a computer in the AD group that builds the collection but then I remove the computer from that group. Can I have it automatically remove it from the collection?
  5. Wouldn't the task sequence be used for an OSD? How would I do a wrapper script?
  6. We currently use Group Policy to install software and are moving to SCCM 2007. I've done a little testing with packages and SCCM will reinstall the software if it was installed by group policy. Is there a way to have it so that if the software is already installed, SCCM won't reinstall it?
  7. What is the real difference between these two? Should I use Package from Definition whenever installing with an MSI file? (I.E. Adobe Reader, Symantec Endpoint Protection, etc). Should I deploy Office 2010 this way using ProPlusWW.msi located in the ProPlus.WW folder?
  8. Is there a specific reason to using New "Package" instead of New "Package from Definition"?
  9. How do I create a collection that includes all computers in a specific OU? My AD structure is like: Domain -USA -Site1 -Clients -Servers -Users -Site2 -Clients -Servers -Users -Canada -Site1 -Clients -Servers -Users -Site2 -Clients -Servers -Users Etc. I want to create a collection that contains all the objects in USA-Site1-Clients. How do I do that?
  10. How do I set this up so that it will see new members of the group quickly (within 15-30 minutes of the computer being added)? Does ConfigMgr need to run the Active Directory System Group Discovery, then update the collection?
  11. I have a parent/child domain setup. Everything is in the child domain except for a couple root domain controllers. Do I need to create the System Management contain in cn=system on the parent domain or the child domain?
  12. What about my question regarding the schema extension?
  13. I'm setting up SCCM 2007 and have a somewhat unique situation. We are currently in the process of consolidating two domains into a single, new domain. In the new domain, we have a root domain with nothing but a few domain controllers and a child domain which currently has some domain controllers, a few Exchange 2010 servers and some other small servers. It will eventually have all the servers, computers and users from the two old domains. I'm going to set up the SCCM server in the new domain. Since we don't have any SQL servers in the new domain yet (and don't want to create new ones, we will migrate the current ones at some point), I don't have an SQL server to use. I think I have 3 options, but only two optimal. 1) Install a new SQL server on the new domain (Don't want to do), 2) Install SQL Express on the SCCM server and move the database once the SQL servers are moved (How are is this to do?) 3) Use an SQL server on the old domain (Is this possible?) What is the best way to go? On a side note, when extending the schema, do I need to extend it on the root domain or just the child domain?
  14. I've been tasked to implement SCCM at work. Right now, I just need to deploy software to one site but it will eventually grow to deploying software, Operating Systems and Windows Updates to 13 sites around the world. Is it possible to just set up the software distribution now and then grow it out?
  15. Is there a way to stop the New Hardware Found wizard from showing up when using MDT? I am using the Lenovo Thinstaller to install software/drivers on to the laptops but it stalls when it tries to install hardware, it stalls until I cancel out of the wizard.
  16. I'm looking in to using this with MDT (no SCCM). Does anyone know if it is possible? How do you set the timeout in MDT?
  17. That would only change it for the current user. Is there a way to change it for the entire machine and/or default user?
  18. Does anyone know what needs to be changed for the locale?
  19. Does this work with just MDT (no SCCM)?
  20. The WIM is of Windows XP and DISM doesn't support XP, correct? Is there a way to do it with ImageX?
  21. Is there a way to change the locale on computers that I am deploying on MDT? I am setting up MDT in Australia using an image that currently has US set for it's local.
  22. How do I set up my TS so that it will automatically log on a certain number of times in order to finish everything? I have AutoLogon = Yes enabled in both my sysprep.ini and unattended.txt with the AdminPasswd. I'm trying to do this in my Win XP image.
  23. Yes. It is on the DP and the SMSPXEIMAGES$ share.
  24. I have a secondary site setup with Server 2003. I am having an issue with OS deployments. I am using bootable media instead of PXE, I can't try PXE until tomorrow at the earliest because of the setup. Anyhow, my log says that it can't find the package that contains my boot.wim file. The file is there and permissions seem to be fine (I.e. the permissions are the same as they are on my primary site server). Is there something special that I have to do on my secondary servers? I can PXE boot and deploy in my primary site fine. I've attached the smsts.log file. smsts.log
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.