Jump to content


GarthMJ

Moderators
  • Posts

    1,939
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by GarthMJ

  1. If you can't do it with wbemtest test then you will not be able to do it with Client Center. There must be some sec policy in place blocking accesses.
  2. So just for clarification. Can you deploy SU to these PCs now? What Classification have you enabled?
  3. I'm confused about what the problem is, in CM12 the db will start with 5GB and grow. I would just watch the drive and only worry about it if grow much more.
  4. That is a political reason not a technical reason, however since you will have a CAS and the best practices if for them to do their management from the CAS only. How will this be any different then having just a single primary? By removing the CAS, you are reducing the complexity of your environment and save the HW cost too.
  5. Honestly, I would worry about price so much as functionality and learning curve. Your packaging team should have a much better idea of all of the available options and even if they didn't, they are the ones that need to create the package with the software, and can tell you which one is better for them. Or you can buy new software for them but if it take 6 months or longer for them to get a good (not excellent but good) understanding of the SW. Then are you really saving anything? Honestly, I would upgrade what they currently have to the latest version or make them evaluate the packaging software out there.
  6. Have you looked at the built-in reports, particularly "Count of all instances of software registered with Add or Remove Programs"?
  7. Does the IP address resolve to the right IP address for that client? Are you sure? If you do an nbtstat –a <ip> are you getting the NetBIOS name of the PC in question?
  8. CM07 will not retry this install. You will need to re-advertise it or create a new mandatory schedule time for the existing advert.
  9. So are you trying to use CM07/CM12 to deploy the SU for you, or are you trying to use WSUS to deploy the SU for you? You can us WSUS directly to manage your server, use a GPO to override the SUP location details. Keep in mind that you cannot use CM07/CM12 to deploy SU to these server any more then.
  10. So I’m a little confused. You want and 800 MB page file on C:\, but what is the script for then? It your call but IMO 30 GB is tiny for a C:\, everyone who I have seen with tiny C:\ always run into issue at some point and need to increase the C:\. A while back I have a doc that listed that you should have 25% free disk space on C:\ for performance reason, I don’t have it any more. Personally, I will not make a C:\ less than 100 GB. HD space is cheap and I don’t need the headache of constantly clean it (C:\) up.
  11. So not answer your question fully… Can you do everything natively within CM12? Sure but that assume that you never deploy any bad applications and/or you never want to customize the application, i.e. Make the setup promptless, change a setting or two, etc. IMO, You will get lots of suggestion as to what you should use but based on my experience, you should talk to your packaging team and get them to evaluation all the options and find the right one for them.
  12. I wouldn’t put up a CAS, I would have a single primary and maybe a secondary or two. It would really depend on what the network look like.
  13. Personally, I would look at adding IE to your Software Update, this your make your life so much easier.
  14. How many user do you have? Is reason why you can’t use RBA for this? Remember that a CAS will not prevent Admin from deploying SW to the other company.
  15. CM12 using the Local System account to install applications, therefore if you need it to access the internet, you need to enable all machine accounts to access via your Proxy. How you could create a Task Sequence and define a execution account, this would mean that you need 1 account to access the internet. Test- Test – test… Personally, I would contact the vendor and ask them for advise on how to roll out their software in an automated fashion.
  16. If the permission are setup correctly, it doesn’t matter if you execute it on a DC or not. Try adding yourself into Enterprise admins. Are your DC Windows 2000? Or did they get upgraded form Windows 2000?
  17. 30 GB is a tiny drive size. If this a VM why not use a Dynamic VHD set to 128 GB or something like that. Now is that 30GB just for SQL or is that 30GB for SQL and all its database? My 20 PC lab have a db of ~10GB. For production db, it will depend alot on how many PCs you have, so How many PCs will you have?
  18. That query does not use SW inv for it data, it use HW inv. But again why not use Software Update to deploy this SU?
  19. Why don’t you use Software Update for deploying this SU update? You can change you HW inventory cycle to daily and therefore it will take 24 hours for everyone to start reporting updated data back to CM12/CM07.
  20. This is not answer your question directly, but one of my client created a web interface to allow the Service Desk to delete PC from CM07/CM12. Since it was a web interface security was control at the website and one 1 account has access to CM07/CM12. Also by using the web interface they controlled what they could see there too.
  21. There is no simple way to do this, you would need to write your own application/add-on for the CM12 console.
  22. IMO, 800 MB is not enough free space on C:\, IMO you should have a minimum of 100 GB (total space) on C:\. Otherwise you will have problem with SU and will constantly be cleaning the C:\ to get more space. You can query WMI to get the physical Ram then you can multiple that by 1.5.
  23. Did you rename the server after installing SQL? Is both the CM12 database and the SQL server SQL_Latin1_General_CP1_CI_AS collation?
  24. That would be Heartbeat discovery and it should never been turned off.
×
×
  • 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.