Hutch

No I'm not. Since I deleted and recreated everything the new deployments are behaving differently. Now when I run the Application Deployment & Evaluation Cycle, from the console or the client, I am told that it was successfully triggered but it looks like it never starts because no log file is generated. I also no longer lose the cycles under the action tab like I used to either. I don't see any problems in the log files except for right around the time the computer would be finishing the OSD or during reboots which I feel I can ignore.

I created a new upgrade package using the "Microsoft Configuration Manager Client Upgrade 6.0 ALL" definition and used it in my TS. Didn't help.

I don't provide any installation properties in the TS but none seem to be required. The site code is immediately visible in the Configuration Manager Control Panel after OSD completes, and within ten minutes I see all of the cycles listed under the Actions tab. The Software Center is displaying my corporate name rather than IT Organization so it has the default client settings as well. This new image is behaving slightly differently. I deployed this image yesterday morning and although I ran the Application Deployment and Evaluation Cycle on it a dozen times throughout the day, the log file was never created. So now instead of behaving badly, it's not running at all. It did however run overnight and all of the apps are now visible in Software Center and the log file is there. They didn't install so I guess they were discovered outside of the maintenance window. A couple of things I would like to know is: Does it matter if Windows is not activated? I have MAK licenses so I'm hesitant to activate Windows knowing I will be deploying test images another 20 times trying to get this working. Should I be installing "Configuration Manager Client Package" or "Microsoft Configuration Manager Client Upgrade 5.0 ALL"? All of the tutorials I have seen use the upgrade package which doesn't make any sense to me. I have tried both with the same results but I would like to know which is proper. Both have the same Source location but they have different Source versions. The upgrade is 1(2013-04-15) and the Package is 6(2013-11-26). There is only one set of source files in that folder. I just noticed there is a "Microsoft Configuration Manager Client Upgrade 6.0 ALL" package definition as well.

I have rebuilt my image from scratch and I am still having this problem.

They are false and empty as you described.

Did not solve the problem. Two and a half hours after I was able to log in, all but two of the cycles in the actions tab have disappeared. They will all be there by tomorrow and everything will be working but this is totally unacceptable.

Of the eight apps, the two hotfixes are already installed in the image. The other six apps are not but I should still see them in Software Center. The hotfixes don't always show up in Software Center but sometimes I see one or both of them. I had automatic site-wide client push installation enabled so I turned it off in case that was causing the re-installation. Will report back if that solves the problem.

Hello I have an OSD issue that is driving me nuts and hopefully someone out there can shed some light on this for me. This is a typical scenario: OSD runs as it should and everything in the new computer works fine. If I open the Configuration Manager Control Panel I see 11 cycles in the Actions tab. If I open Software Center I see my Corporate name instead of IT Organization so it is talking to the MP and receiving policies. I see the computer in the console and in the appropriate collections. The problem is that none of the applications required by the new computer will install. There are at least eight apps, depending on which collections it is in, two of which are MS hotfixes. These hotfixes are already included in the image and one or both of them may show up in Software Center as installed so App Discovery is running and detecting one or both of these two apps but not the other six. All applications are configured to install outside of the maintenance window. No errors in AppDiscovery.log About three hours after the OSD has completed the Configuration Manager Control Panel loses its Configurations tab and the cycles under the Action tab start to disappear until there are only two left. The User and Machine Policy Retrieval & Evaluation Cycles. It takes a day or two and then the cycles all come back and the apps will install. Everything is fine from that point on. Obviously three days to deploy one computer is unacceptable. Has anyone else experienced anything similar to this? Some pertinent information: SCCM 2012 R2 with MDT 2013 - all roles on one server except database Tried WMI v2.0, 3.0 and 4.0 Installed hotfixes KB2775511 and KB2889748 in the OSD image OSD image is up to date with patches and updates Hardware doesn't matter. All computers are Dell but it happens on four different models Tried adding this reg key in the TS as per this article: HKLM\Software\Microsoft\CCM /v UserPolicyReRequestDelay /t REG_DWORD /d 6000000

Hello Ever since upgrading to R2 I have two entries for every new computer I deploy. The way I deploy computers is: Start a PXE boot on the new computer and pause it once the MAC address is displayed Go to SCCM console and use the Import Computer Information wizard to enter the computer name and MAC address and add it to my OS Deploy collection. Resume the PXE boot on the new computer. This procedure used to work fine with SP1 but since R2 I end up with two computers after the task sequence completes, one with a client and one without. Has anyone else seen this issue and is there a fix for it?

Anyone?

Hello I am trying to delete an application (app1) but keep getting this warning: Configuration Manager cannot delete this application because other applications or task sequences reference it. It goes on to say that the number of dependent applications is 1 and if I go into the References tab of app1 properties, I can see the dependent application (app2). The problem is I have already deleted app2. Is there anything I can do to delete app1 or am I stuck with it forever?

Everything is working now after regenerating the certificates, except for my Enrollment Point but I think that's unrelated and will start a new thread for that. Reinstalling the client isn't necessary. Even though I stupidly tried to restore my site without properly researching the proper method, others may find themselves having to restore the database for some other reason and find themselves in the same mess I did so this could still be a useful thread for someone.

I think I was just impatient. I reinstalled the client on two computers and they are both downloading policies now. Hopefully it would have happened anyway and I don't have to reinstall everywhere.

I deleted all the server certificates as per this article and rebooted to recreate them. That fixed my "Signature verification failed" error from the PolicyAgent log. I don't see any errors anywhere now except for the Enrollment Point but I don't care about that right now. Since regenerating the certificates on the server, the clients now have new symptoms. No more policy errors but they aren't receiving policies. In Software Center it says IT Organization instead of the company name I defined in the default client settings. Also the config Manager Control Panel Actions tab only shows Machine and User Policy Retrieval & Evaluation Cycles. Nothing else.

No. Didn't know about it. I just backed up the database in SQL Server Management, uninstalled SCCM, reinstalled SCCM and restored the DB.

I have a single server site that I had to rebuild so I backed up the database, re-installed SCCM 2012 R2, then restored the database. To my dismay, when I opened the console, all of my hard work was missing. I learned that ownership of the database is changed to the logged on user when backing it up so I changed that back to sa and to my joy, when I opened the console, all of my previous configurations were there. The joy was short lived however when I found that nothing was working. After much tinkering, then giving up and recreating my boot images, OS image, deleting everything from the server, then distributing and deploying the new images, I am finally able to deploy an OS, but that is where I hit a brick wall. I cannot get updates or applications out to any computers, regardless of whether the computers were deployed with the original or rebuilt configuration manager. Rebuilding an application from scratch doesn't help either. The only issues I see in Component Status are with the Enrollment Point, which I am not using but I mention it here in case it is related to my issues, and SMS_INVENTORY_DATA_LOADER. The SMS_INVENTORY_DATA_LOADER component shows this warning: Inventory Data Loader failed to process the delta MIF file "XH7VAWI77.MIF" and has moved it to "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\NonExistentRow\t1mncg1b.MIF." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun. The SMS_ENROLL_SERVER component is reporting this error (IIS is configured to listen on ports 80 and 443 with a valid certificate): Enrollment Point Control Manager detected that the Enrollment Point is not responding to HTTP/HTTPS requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which Enroll Service is configured to communicate. On the clients: PolicyAgent.log is loaded with this error: Signature verification failed for PolicyAssignmentID execmgr.log has this warning: Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client No errors in LocationServices.log or ClientLocation.log so it is talking to the MP. Devices show up in the console as Active with recent heartbeats and policy requests. I have spent far too much time on this. I hope someone has a solution better than the wipe and rebuild that I am contemplating.