Jump to content


PaulWhite@pickens.k12

Established Members
  • Posts

    36
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by PaulWhite@pickens.k12

  1. I upgraded my lab to R2 and created a build and capture but when I start my VM to capture a new image I do not see the task sequence in the list. I do see my old task sequences to deploy windows 7 and server 2008. I have made sure that everything is distributed and I am banging head against the wall on this one. Any thoughts, Thanks
  2. Maybe I just don't understand but I created the powershell script version of this as well and I still get the same results. The collection has no clients assigned and the task sequence is deployed as required. I move a client into the collection it runs, task sequence completes and the client just sits in the collection. What is the trigger to run the status rule, What makes the rule run that in turn runs the script to remove the client from the collection. I really need this to work. Jorgan if you are out there I could use the help. Thanks
  3. I have built a collection with no clients assigned and have a task sequence deployed to the collection to re-image the clients that are placed in. I have followed the steps to create the script and status filter rule. In my case it does not work, and I don't know why. I followed the instructions to the letter and even went through them several times. What am I missing? Does the task sequence have to be a MDT, at what point does the status rules run, or does when does the task sequence report back the success code? The machines work fine and I did have to change the deployment rule to only re-run if it failed otherwise it would just keep running. Should I abandon this method and use the powershell version instead? Anyone have this and overcome it? Thanks https://mpgnotes.wordpress.com/tag/remove-a-computer-from-a-collection-when-osd-task-sequence-is-completed/
  4. Another question you said others users cant get to the SCCM server, do you me to the console or to the software portal? What credentials are you using to log into the console from your computer?
  5. That sounds like you have something going on between the SCCM server and the datbase. Or it could be a network issue, if I connect to the console at work you can see the console trying to connect to the database as it does what I call the strobe thing, it sorta flashes the "connecting to site database XXXX" about 4 times, if I do it on the server itself it flashes once or twice, if it do it from home connected through vpn from my laptop it flashes about 6 to 8 times, which tells me it depends a lot on the network connection you have. How often are you running things like machine policy retrieval, checking for software updates, are you doing backups using any third party software early in the morning, I Use altaro to back up my systems every night as the server and database are both virtuals on the same box and had to adjust the times to offset the backups by about 3 hours and I also check for updates every night. I try to do things in the 6 pm to 2 am time frame so it has time to recover before I come in in the morning. Is this a standalone primary, virtual, is the database on a separate box?
  6. I would love to know the answer to this as well, I have built many applications and if I have a msi for the program it really seems to be the best solution. I have also built many packages and they seem to work better if the program is a larger install for example I built office 2010, 2013 and all of the Autodesk products, Autocad, Revit and Inventor as they were all over 7gig in size as packages. But what really determines whether it is a package or application?
  7. I just wanted to follow up on this as I did find the issue and someone else may have this issue one day. Bits had been disabled in IIS for the incoming site. Here is a screen shot of the box that had been unchecked.
  8. Hardware inventory stopped around 2/5/14, I don't know why. Everything looks like it should in the logs? I really need this to work. What is really weird is I can change classes in the default client settings but they do not change what is reporting. I removed active sync days ago but it does not get taken out. I have a scan scheduled for once a day.
  9. for some reason Kb2859537 causes our client computers to hag on boot at applying user policy, so I do not deploy it, so I thought. We have recently started using the imaging in config manager and one of my techs discovered the update on some x32 machines and the update had been applied to the x32 image. I created another image and then had to come up with a way to remove it from the machines that had it. In my lab I turned on win32_"QFE" and was able to build a collection showing the 3 machines I loaded it on, I created a task sequence to remove it using wusa silent uninstall and everything worked great. In production I have turned on QFE and I am still not seeing any machines reporting in hardware inventory. Any thoughts?
  10. Got it! My config manager server time was off. My server and sql both run on the same host, The host is not joined to the domain and does not get it's time from the ntp that the clients and domain controllers do. After going back and looking at the system components I saw that there where a lot of errors that indicated there was a 310 to 470 second difference between the the server and clients and there were not reporting back to there server( I wish I had taken some screen shots). I corrected the time on the host and pointed it to the ntp we use for the domain and was able to install the admin console on a pc. I don't know why there was an 7-ish minute time difference between Microsoft time and our ntp. Go figure
  11. I built a application for the admin console today and when I deployed it to my test group I got this error. I have gotten this in the past if the users were turned off in default client settings but not the issue this time.
×
×
  • 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.