Jump to content


GarthMJ

Moderators
  • Posts

    1939
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by GarthMJ

  1. Have you re-installed the SUP and WSUS yet?
  2. Having two primary sites will NOT help you within a DR situation. You should restore the site. Do you have over 150,000 client's, if not you should one have a single primary site.
  3. So if the install is an MSI you can still us that detection for an Application. Yes you are right you will need to pass the exit code from the setup to the batch file, vbs, PowerShell, which in turn pass it to CM12.
  4. I agree that I would not likely have one big ZIP (for 10GB package) but break it up into bigger chunks. (Maybe 100 MB zip) If done right the your will NOT loose the application detection
  5. I hate to say this but this is not a CM12 issue it is a Cisco problem. Have you reviewed the Cisco logs.
  6. Why can't you create a zip with all the file and then create a batch file, VBS or PowerShell script to unzip and trigger the install?
  7. There is a lot more too it than just Edit AD and fixing a few service accounts. To truly do this, you need to edit both the database directly and site control file. Neither of which is supported by MS unless you use their SDK. The plain and simple fact of the matter, if you ever have problems and CSS determines it is because you renamed your domain/forest. they will wipe their hand of the whole thing. It is far simpler to just create a new CM12 environment, Migrate everything and re-assign the client then trying to Rename your domain/forest. At least creating a new CM12 Site mean you are guaranteed to be supported by CSS.
  8. If MSTSC doesn't work on these computers, I would fix that then worry about CM12 and it RC.
  9. lol, Don't worry about it.. I think that I will see him next week at IT/Dev Connections. BTW he is from the UK too. ;-)
  10. BTW, Is this Farmer Phil?
  11. In a nutshell, you would do it the same way you manually uninstalled the SCEP client. There are lot of different ways to do this but this is one of the simplest. Create a Program with the Uninstall for SCEP client Create a Program with the Install for SCEP client Deploy the Uninstall for SCEP with a time of 11:00am Deploy the Install for SCEP with a time of 11:02 You can you task sequences to make this one "step" or you can use dependences too. In any case you will need to test this.
  12. I personally, like Client push and have never seen any issue like what Phil is talking about. However, NONE of my client have the Automatic push enabled. They all enable the CM12 client via OSD, computer startup script or they manually push them as they find them. I would never recommend using GPOs as this will cause problems later.
  13. I wouldn't say consider it, I would say it is a bare minimum to have 16GB of ram.
  14. What you are asking for is a complicated task, as such I would hire a CM12 ODS specialist to work on this with you. I still don't understand your need to have a workgroup computer, IMO, it doesn't make sense. Why does it matter, that it is domain joined or not? My laptop is domain join but when I use it on a plane, it just can't access any domain resources. If I logon locally to laptop it would ask exactly like a workgroup computer. So, can you see why I don't understand your need. BTW, CM12 itself doesn't support dual boot computers either, so if you are trying to manager it with CM12, you will like have issues.
  15. Start with the easy one, What happens when you try to manually install the SU it on of the computer which it failed? The unknown status is generally due to a GPO conflict.
  16. Have you reviewed the logs? Why can't you use CM12 to uninstall SCEP and re-install it?
  17. OK I will bite, why would you want to do that? I’m saying that because a Domain joined computer has the exact same functionality as the Workgroup computer. Therefore, How will that be useful at all?
  18. IMO, you already have the documentation you need. You can see that PXE is taking a long time as these remote locations, If you add a remote DP with PXE, you are sure that the time will be reduce to something that the other team will like. The only thing that I would do, is try to temporarily add a DP with PXE at that site and see to confirm the results. It will then be hard for anyone, including management to say, you are wrong.
  19. I would keep SQL local, it will save you a ton of headaches. FYI, I add 15 days to contract when SQL is remote to CM12, There are just too many headache.
  20. Out side of PXE boot are you seeing any other issues with APP or SU deployment? How many computer are at eh branch office? Why do you need to PXE boot there at all? Why not ship the computer back to the main campus and fix them there?
  21. So can you clarify what you mean by Manual push vs push? How exactly are you expect the CM12 client to get pushed to these clients? Do you have Auto-push enabled?(it is not enabled by default) What happens when a new client is discovered? Do it show up within the CCM.log?
  22. Q1: yes Q2: IPHelpers, talk to your networking team about this. Q3: Yes; sortof, you still need to create it at your primary site but then you can deploy it to only the secondary sites. Q4: They are all management from the primary site. Q5. No. You don't need a CAS.
  23. This is not practical, I'm not even sure it is doable, without a lot of intervention from you. Why not use Reports? Why use Queries (WQL)? What is the Business case for this?
  24. I'm not a fan of AD boundaries either because of the short cuts most AD admins take. What exactly do you have define for your AD subnets? For example 192.168.101.0/22 What is your clients IP address and more importantly subnet mask? For example 192.168.102.134/24
×
×
  • 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.