surfincow

Was able to figure out the problem. It appears that two certificates were bound to the same port somehow. Removing the extra cert fixed the problem. Reference: https://social.technet.microsoft.com/Forums/en-US/b853fdc4-61ba-4971-b737-3c441ea17e6a/application-catalog-site-cannot-connect-to-the-application-server?forum=configmanagerapps Thanks

Hello, Have built a new configmgr cb system and I'm running into issues with the application catalog. Server 2012R2 & ConfigMgr Current Branch and we use SSL for all communications (except SUP>WSUS uses HTTP) With the new configmgr, the application catalog as mostly gone away as user targeted apps will now show up in the Software Center. I tested deploying a package to a test user but it never appeared in the SC. To see if it is getting deployed correctly, I clicked the link to directly access the application catalog. I opened the link to the Application Catalog, and am presented with the option to activate Silverlight, but then get: Cannot connect to the application server. The website cannot communicate with the server." Looking at this https://blogs.technet.microsoft.com/configmgrteam/2012/07/05/tips-and-tricks-for-deploying-the-application-catalog-in-system-center-2012-configuration-manager/it referenced checking for ServicePortalWebSite.log & ServicePortalWebService.log. Since this was for 2012 I checked against the list of log files for the CB version and those logs are listed as "should be there". On my system they were not. So I removed the 2 roles (App Web & Service Point) then reinstalled. After installation the same error is present and still neither logs referenced above are present. Reviewing the SMSAWEBSVCSetup.log, SMSPORTALSetup.log & awebsvcMSI.log & portlwebMSI.log I don't see any errors. I've found some info searching but its difficult to find version specific material now that the product has such a generic name. There was some references to activating ASP4.0 but looking at the logs, it states its activated. Other than that, I'm not really sure where to go. I'm wondering if anyone has encountered this and knows what might be the problem? Thanks ---edit: I did eventually locate the S|ervicePortalWebsite.log & ServicePortalWebService.log logs and do not see any errors in either

Hello, Not sure how the automatic client update thingy works, but looking at your logs I'm wondering if its a package that's been advertised? AFAIK using the client automatic update shouldn't cause a reboot. Not totally sure since we deploy those through WSUS but if its a package, perhaps the package was mis/configured to reboot after install? Might check your packages and see if you have something with that name (Configuration Manager Client Upgrade Program and advertisement HOL20000]) and its advertised to some collection?

Hello, I'm currently looking to pilot the software with Parallels and am wondering if there is any documentation anywhere that states this won't affect Microsoft Support w/SCCM (non-mac related things) in the future? I know one way to get MS to wash their hands of your issues is if you mess with the DB. I don't believe this product does that since it creates its own DB to store its information. So far the sales rep and technical sales rep have been unable to provide anything in writing or a link that states MS won't drop support if this product is used. While I would be very surprised that is the case, but I'd rather have some sort of proof before proceeding. Any idea if such a thing exists? Also, how have you found their support to be in general (if you've used it)? Are they quick to respond to problems and get things fixed/resolved fast or is it a headache to contact them? Thanks

Hello, Yes I am sure. I even exported the settings and the ones I imported are there.

Hello, Recently had a request to obtain details information about MSSQL installs across the organization. This information isnt collected by SCCM by default so in order to get it, you need to extend the hardware inventory settings. Originally I found these directions: http://myitforum.com/myitforumwp/2012/02/21/installed-sql-05-sql08-and-sql12-version-information-via-configmgr-hardware-inventory/but after the query failed to run, I started to search for another option (I eventually got the query to run, it failed originally due to formatting issues on the webpage) and found this http://mnscug.org/blogs/sherry-kissinger/328-installed-sql05-sql08-sql12-sql14-version-information-via-configmgr-hardware-inventory which is basically the same just updated to include other versions of SQL. I removed the 3 previously imported hardware inventory classes (administration > client Settings > Default client settings > hardware inventory > set classes) then re-imported the 4 classes in the new article. I went to run the query again in SQL but it fails with the error: Synonym 'v_gs_sql_property_legacy0' refers to an invalid object. I'm not sure what the problem might be. Nothing in the DB was modified directly so nothing should have broke. Any idea what might be the problem? SCCM 2012R2 SP1 MSSQL 2008R2

Found the problem. On the DP properties > PXE Tab "Specify the PXE Server response delay" was configured for 30 seconds. Changing that to a lower number, "5 seconds" in this situation fixed the problem.

For both the x64 and x86 "Deploy this boot image from the PXE enabled distribution point" is checked. We do only deploy 64bit OS's but both the boot image for both are distributed. For the DP properties, Enable PXE support for Clients and allow this distribution point to respond to incoming PXE requests is enabled.

Yes -- also, to make things simpler, I'm trying to pxeboot another machine in the same network as the DHCP and SCCM/PXE box. This should eliminate any network config issues since everything is within the same network. So this sounds like something specific to the SCCM DP and the PXE service not working right? Its pretty clear that the traffic is hitting the sccm box because of what I see in the logs. For some reason though its not picking it up and offering PXE services. I just don't understand how removing the incorrect configuration caused things to stop working. When DHCP was directing the client to the DP, everything worked. Now that it is configured per MS spec, it does not.

Hello, So I had the ip-helpers set to forward traffic to the DP handling PXE, remove the DHCP scope options and BIOS PXE boot works intermittently, and zero success for UEFI. Only information in smspxe.log is <mac>,<guid>: not serviced. Any thoughts?

Hello, I've been doing PXE boot installs for Windows 7 for the past year and everything works fine. With the move to Windows 10 (x64), we plan to use UEFI rather than BIOS and also enable Secure Boot. I started playing with this today, and on my test machine, enabled UEFI, disabled Legacy ROM support and enabled SecureBoot. When I started the machine, it failed to download the boot image stating "pxe operating system loader failed signature verification. warning the file may have been tampered with". I decided to skip secure boot for the time being and focus on UEFI. When I pxe boot using UEFI, the screen displays: checking media presence, media present, start oxe over IPv4 The screen briefly flashes "Succeeded to download NBP file (this message goes by so fast the only way to see it was to make a video and pause at the point where it showed up. Image was blurry so NBP could be the wrong letters) then checking media presence, media present, start oxe over IPv6 finally goes to No Bootable devices found. I've never been able to find clear and consistant information regarding setting up PXE, DHCP and configuration manager. The way I have it set up is from various articles I've found. One thing I am unclear about are is, what the correct DHCP options should be. DHCP is running on a host separate than the distribution point which is running the WDS service. I have configured DHCP option 66 = fqdn of the configmgr server which is running WDS 67 = smsboot\x64\wdsnbp.com I also have option 60 configured, which at present, has the IP address to the primary configmgr server. Looking over several documents, I'm not sure if this field is needed. I've seen references that indicate you only need this configured if the DHCP server and WDS server are on the same box. I've also come across another document stating that the value should equal "PXE Client". Any idea what this value should be, and if it is needed in our envirnment? (All servers are w2008r2 sp1) In regards to PXEbooting UEFI and BIOS, is configmgr/wds smart enough to direct the client to download the correct file when pxebooting? (can it support both BIOS clients and UEFI clients via PXE or is it one or the other?) Am I missing something in DHCP that allows UEFI to boot via PXE? Once I'm able to get UEFI sorted out, what is involved to get OSD working using PXE with SecureBoot enabled? Thanks!

There's a specific hotfix for this for 2012R2SP1, but its included in the CU1 https://support.microsoft.com/en-us/kb/3074857 Install that and it should fix the issue.

I deploy the initial install as an Application so the mms.cfg gets included. Subsequent updates are pushed via SCUP. I've noticed that updates show up in SCUP a day or two sooner than on the public download site. Considering how many issues there are with Flash, getting updates out ASAP is a good thing

Hello, I found two articles that discuss the migration path. 1) http://blogs.msdn.com/b/beanexpert/archive/2015/08/05/how-to-switch-to-windows-10-adk-on-configmgr-2012-r2-sp1.aspx 2) http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx Both appear very similar, but option #1 had less manual things to do. I went ahead and did it and so far everything appears to work.

According to this https://technet.microsoft.com/library/mt131422.aspxit says it should be supported.

Hello, After performing the upgrade from 2012R2 to R2 SP1, I found quite a number of things broke. Application Catalog, Boot Images, Client Registration, Inventory Data, PXE to name a few. I have fixed most of them, but now as I go to push out some critical patches, I noticed that updates downloaded from WSUS since the upgrade are not making it into configuration manager. Looking at the wsusctrl.log and also WCM.log, I see Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701 every 8 hours (the sync schedule) I found some posts with users having similar issues. One of the suggested fixes was changing the WsusPool in IIS to use .net Framework from v.2.0 to v.4.0. I'm not sure what kind of affect this might have so I'm wondering your thoughts? As far as my upgrade goes, the SQL DB test didn't have any errors. The install itself was OK; however there are some references to .Net registration with Fx 2.0, but successful registration with .Net 4.0 INFO: Registering F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8) CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll" Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8) CTool::RegisterManagedBinary: Failed to register F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll with .Net Fx 2.0 Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8) CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll" Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8) CTool::RegisterManagedBinary: Registered F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll successfully Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8) Would this indicate it failed to register with 2.0 but with 4.0 is was successful? Therefore, possibly the suggestion to change the IIS settings would be correct.. but not sure why configmgr setup didn't set that to the correct value automatically. One strange thing, I can publish updates from SCUP without any issue, its just updates downloaded by WSUS from MS that are not working. Any thoughts?

Hello, Turns out the msi installer would prompt to kill explorer and attempt to restart it or perform a reboot after install is complete. Since the windows were not shown (due to it being suppressed), explorer was killed but was unable to remove it. After trying many numerous msiexec /x $flag's the problem still persisted. The end solution was to use wmic to perform the removal. "wmic product where name='$product' call 'uninstall'"

Hello, I have a particular application that I need to remove. There appears to be some bug (most likely with the app) where when you run msiexec /x product.msi, the explorer.exe (desktop/start menu) process is killed. I have line in the script to detect if explorer.exe is running and if not, to start it, but the problem I am running into is that it is not starting explorer (desktop/start menu) but a normal explorer window (file browser). This only appears to happen when the ccmclient is executing the command. For example, if I manually kill explorer.exe and then restart it (either from task manager or from cmd prompt) the task bar and desktop return. If I do the same via a Package/Script an explorer window (file browser) appears. This seems like such a simple task and it works with other applications; however, for explorer.exe it does not. (in the example below, replace explorer.exe with notepad.exe and it works) Any idea why this isnt working? All hosts are Windows 7 64bit, and the script is running as user, not administrator. -How the process is started if not running cmd.exe /c tasklist /FI "IMAGENAME eq explorer.exe" | find /I /N "explorer.exe" || start explorer.exe Also, specifying the full path to explorer.exe does not work either. Thanks!

Hello, I am wondering if anyone here is currently using the Parallels plugin for ConfigMgr for managing Mac workstations? I know that there are some built in features within ConfigMgr to handle some basic Mac management, but the feature list and simplicity of this add-on looks quite promising. Just curious if anyone here has any experience/feedback with this product? Thanks

What if you try: taskkill /F /IM remote-viewer.exe /T %windir%\Sysnative\wmic product where "name like 'VirtViewer%%'" call uninstall /nointeractive exit /B %EXIT_CODE%

Hello, If you are using automatic deployment rules for this you can add "custom severity = none" in the criteria for your software updates. Then, on the individual update you do not want to distribute, set a "custom severity" to that update (anything other than "none"). Since your rule targets updates that do not have a custom severity set it should not download/deploy it. This assumes that you are using ADR's and not currently setting custom severity for updates.

Dunno if your problem was resolved but if not, this may help: http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx

Hello, Thank you for your reply but it does not address the client installation method we've chosen to use. If there is not the option to install the client via WSUS, then the client won't get installed. Our environment is such that the push install from the console will not work. I've found the GPO install of the client to be flakey as well. The only method that works well is the SUP Client Install. So again if we are using this method to install the client, that means that the workstation will always display both the configmgr reboot window, and the WUA reboot window?

Hello, I actually saw these yesterday and they are part of the confusion. In the 2nd blog, it talks about disabling automatic updates. If this is disabled, then SUP based client install won't work. Since one of the installation methods provided is a SUP based install, this needs to be enabled. So is it by design then that using the SUP based install methods the end user will see the reboot window presented by the WUA agent and also by ConfigMgr? That seems odd. Thoughts?

Hello, I'm having an issue trying to figure out the correct combination of GPO settings in regards to the Windows Update Agent and Configuration Manager. In our environment, we use the Software Update Based Client Installation Method. There is a GPO configured that points the computers to the WSUS server that holds the client. If the client is not installed, WUA detects it as being required and installs it. It works great. The problem I am running into is that because WUA is enabled on the computer (to receive the initial client installation) when I deploy monthly MS patches, the end user not only gets the reboot window from ConfigMgr, but also from WUA. I'm seeing conflicting information regarding if WUA should be enabled or not if you are using ConfigMgr for updates. However; since WUA needs to be turned on for this particular client installation method, turning it off isn't much of an option. (and I can't imagine it is part of the design that users are expected to see two different reboot windows after patches are installed). Basically I need to know what the minimum required GPO settings are so that: The client is installed via WSUS if not currently installed (happens ASAP without any user notification) Once the client is installed, the only reboot/update notification the end user receives is from the ConfigMgr client In addition, allowing signed updates from an intranet MS Update service point needs to be enabled (I know how to do that but mentioning it in case it affects any of the other requirements). WSUS is on the same server as ConfigMgr. So is this possible? I can't imagine that it is not, just not sure how to set it up. Thanks