Jump to content


YPCC

Established Members
  • Posts

    159
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by YPCC

  1. My thoughts too. On prem DP might work. Im not sure if the management point being in the "cloud" will make a difference for pxe boots. Same goes for bootable media. No reason why using bootable media and pointing the DP to azure sccm wouldnt work. Just an added step during imaging though.
  2. Services (whether started, stopped or dsiabled) are collected as part of Hardware Inventory i believe. To check this, search for any device in sccm, right click, Resource Explorer, Services. Should see the services listed and the state they are in. Is this good enough or do you actively need to run "net start trustedinstaller" in order to verify if registry is bad or not
  3. the ccmsetup.log and clientmsi.log should give you detailed info on whats going on. Post them up and lets see
  4. Did you deploy .net 4.6 as a application or using software updates? If application, you should be able to find the information in the SQL database. I'll have a look tomorrow however i know its in one of the tables in the DB. That will help you track down which computer received the install using your application deployment. If software update, that's a bit trickier. Not sure if its even possible as i dont think sccm stores information about how it installed the update. It merely checks if the update is there or not. You can think out of the box however. Depending on how you setup the deployment, sccm might have downloaded the .NET installer files to c:\windows\ccmcache. That means a installer file (.cab, .exe or similar) for .NET 4.6 will be inside the ccmcache folder. You can create a script via sccm and deploy to all machines that scans the c:\windows\ccmcache folder and looks for this installer. If found, exit with 0 so it reports as a success in sccm. If not found exit with a random code like 999 so sccm reports a error. Then all the machine showing success will be the ones you deployed to (or technically, machines that have a 4.6 installer in c:\windows\ccmcache)
  5. Have you trid deloying to a user rather than computer? Im not sure how the always rerun behaves but there could be some logic in having a "always rerun" for a user deployment, thus eerytime a user logs on, it runs. I dont use user deploys much but worth a shot.
  6. Upload the whole logs folder from the client. This looks like a bug rather than misconfiguration
  7. Yup, theres certainly no need to deploy a group with 400+ updates to a OEM windows 7 wim every time you make a ref image. The purists amongst us will hate me for saying that but reality over "best practice" anyday
  8. Not Approve would stop certain elements but best way is to stop and disable the ccmexec service on the machines. This is because a "not approved" machine would still be doing processing client side. If you are getting slowdowns then stopping the services eliminates sccm completely. Be sure to disable it else the service will start again (even if manual)
  9. What client version is installed in the OSD sequence? Is it the client thats designed for your new sccm?
  10. Will try and dig it up and post it tomorrow Powershell is so diverse and multifunctional you should try hard NOT to avoid it. Im no scripter but i managed to write a line of code that deploys a application to a collection at a set time within just 10mins with the help of some googling. It could save you countless hours once you get the hang of it, best of all your management dont need to know you have free time
  11. You're right in saying that could go horribly wrong if the install was deleted and the uninstall wasnt. Why not do something like this: Collection A - Install (add all the machines you need software deployed to here and deploy the install) Collection B - Uninstall (this collection will contain all system but EXCLUDE Collection A - deploy the uninstall here) Example: You have a sccm site consisting of 20 machines Adobe Flash - Install (10 members) Adobe Flash - Uninstall (add the "Adobe Flash - Install" as a exclude rule and then just include the "all systems" collection (or whatever you feel is best)). Then deploy the uninstaller here. Any members of "Adobe Flash - Install" will get the software installed. Any members of "Adobe Flash - Uninstall" will get the software uninstalled One day you decide to remove 5 machines from "Adobe Flash - Install", this will mean they then end up in "Adobe Flash - Uninstall" as they are no longer members of the collection that was excluded Mind you, im sure there are better ways of doing this. I have setup a auto-uninstall mechanism however that's for licensed software and we are using metering. Anyone who hasn't used software "X" in 90 days will get it auto uninstalled.
  12. Powershell. Its a forgotten god send I scripted a 3hour job to run in 10mins
  13. You are correct. That count will only increase if the application has been deployed to it. If the application already exists on machine (but the application wasnt deployed) it wont be included in the count until you actually deploy it. Sccm must query and see the app as being installed before its included in the count.
  14. Resolved, the DNS record wasnt setup correctly. My cname record had the full url (http://xxxxx.cloudapp.net), had to change to the format (xxxxxx.cloudapp.net). In other words, if you cant portquery (443) the azure storage location from the sccm server or the client, its the DNS thats the issue. Works like a dream now.
  15. Try this as a workaround. Build your reference image and apply all the updates into it (e.g. all uodates up to May 2016) Then create a software update group that contains only updates from June 2016 onwards. That way you know your ref image is fully up to date up to May and also you dont have old updates in your update group unecessarily.
  16. Hi all, Was looking for some advice if anyone has worked with cloud dp's. Current situation is: - Have setup a new (first time) DP in the cloud successfully - Enabled the "allow cloud access" client setting - Uploaded the cert to azure - Created a CNAME record to point to the azure service name URL - Distributed a package to the cloud DP succesfully Issue is, i cannot for the life of me get my test client to download from the cloud DP. The error in CAS.log is no DPs were found. The thing with Azure DPs is that i believe they do not need to be a part of the boundary group like traditional DPs. Instead the cloud DP is used as a fallback no matter what the boundary. Any advice appreciated. I am testing the Azure DP by distributing my package only to that DP. If i distribute to my local DP, my client will just download from the local DP instead. Hence ive made sure only the Azure DP has that package. I just cannot figure out what im doing wrong or if ive missed a step somewhere. No firewalls interfering, i suspect its how i have set it up but not sure what.
  17. why not make it even easier and use VirtualBox Works perfectly for me, its free and no messing around with ESXi drivers etc. Just fire up a VM, set the networking to "Bridged" and you're game.
  18. I think he may want all software installed on all machines, listed on a single page. Dont think the built in reports have this, they have a drill down option instead. Quite easy to do, create a query, add computername and "arpdisplayname" from the installsoftware class. Then run it. Depending on how many clients you have, it will bring back a lot of results.
  19. As above simply not possible. I recently did a migration of servers from wsus to sccm. Ensure software updates is enabled. Our group policy was pointing to wsus so i temporarily changed this to point to the sccm wsus instead and ran a software update scan on all the servers. Then 48 hours later changed the GPO back again to point to wsus. This 48 hours allowed enough time for the servers to send all their update information to the sccm database. Maybe this will suffice for you?
  20. Always use a VM when creating a "base image". You can either create the VM manually (using the iso and manually installing windows+updates+coreapplications[flash, java, adobe etc]) or you can automate it using a build and capture task sequence. Once captured you only need a single task sequence. You just add the drivers packages for all your models into that task sequence and set a condition so a driver package only installs for a particular model. Example, if we assume we have 3 seperate driver packages for Dell 100, Dell 230 and Dell 540. Add all 3 packages to the task sequence and set a wmi condition so the driver package for Dell 100 only installs on the Dell 100
  21. So if im not mistaken, you are trting to delete the APP ahc Java x64 application but cannot do so because app ahc java x86 is reliant on it. Your screenshot shows that javax64 is listed in the dependancies tab of javax86. Theres your issue. Java x64 is being used by the Java x86 package. Delete the dependancy and should be problem solved.
  22. Are you using MDT intergation with sccm or just sccm alone? If mdt, go to your customsettings.ini you can add a few lines in there and set the resolution to 1pixel by 1pixel. This will force window to choose the best resolution. I cant reber exact syntax right now but its something like: HRES=1 VRES=1 Could be wrong on syntax so do a quick google and youll find it. If using sccm only, amend your unattend.xml file in the OOBE pass and do the same by setting it to 1x1 pixels. Not tried tbis method but imagine it work.
  23. Dell forgot to mention that they didnt update the drivers for their winpe cab. What version of Winpe do you use? 3.0 or 4.0? If 3.0 you need to download the Windows 7 storage driver for the E7270 and inject it into boot image. If 4.0 you need to download the windows 8 storage driver for E7270 and inject it in.
  24. Regenerate your XML using WindowsSIM. I had this issue when i upgraded to IE11 in my reference image. Apparently IE11 changes the unattend xml schema slightly so i was getting this popup too. Open the XML in windows sim, open your .wim file and find the erronous code. It will show straight away. Youll get some sort of warning like "this feature is deprecated or something". Just remove that section, save, refresh DPs and try again.
×
×
  • 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.