The IDs for each update change during each release. This round, a lot of folks *cough* Kim O. *cough* tried to guess the next number, so they had to change it to something much larger.
$EmbeddedProperty.Value = 171610 So you basically can never use the same script. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of the codepoets Sent: Thursday, December 01, 2016 7:21 PM To: [email protected] Subject: Re: [mssms] 1610 update not showing in console Looks like we got it working. We used a different PowerShell enable than the one I had used before. And this one seems to have enabled the update as it is currently downloading in our LAB. Thanks for the responses everyone. Ivan, I would bet that what you suggested would have worked for us (my colleague used a different one). -Erik On Thu, Dec 1, 2016 at 2:33 PM, Lindenfeld, Ivan <[email protected]<mailto:[email protected]>> wrote: Nah, just kidding around. This is the process we used https://gallery.technet.microsoft.com/ConfigMgr-1610-Enable-046cc0e9 Ivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of the codepoets Sent: Thursday, December 1, 2016 4:36 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] 1610 update not showing in console Actually, Ivan, that is what I was asking about (I hope I didn't sound too demanding, didn't mean to...) :) We're not even seeing the option for an upgrade, so if you are, and you're currently at 1511, that tells me that we probably should be seeing it. Thanks, I appreciate it. On Thu, Dec 1, 2016 at 1:03 PM, Lindenfeld, Ivan <[email protected]<mailto:[email protected]>> wrote: This is not the definitive answer OP is demanding, but our production 1511 site is showing 1610 under Updates and Servicing after running the Powershell script to trigger it. All prerequisites have passed. We are upgrading next Monday evening, so you will have an answer then! ☺ Ivan Lindenfeld Fidelity National From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of the codepoets Sent: Thursday, December 1, 2016 3:46 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] 1610 update not showing in console Again, we are at 1511 in our environment. Microsoft is stating that 1511 should be the minimum for upgrading to 1610. I am asking specificially if anyone has been able to go from 1511 to 1610 directly. Adn yes, I have re-cheched for updates after running the PowerShell. (As this is 1511, I have to restart the SMS_DMP_DOWNLOADER service to do so, as there is no right-click menu). On Thu, Dec 1, 2016 at 11:35 AM, Kamerman, Sol <[email protected]<mailto:[email protected]>> wrote: I just tried the script a few minutes ago in my test environment 1606, and 1610 appeared almost immediately after I checked for updates. Sol From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of the codepoets Sent: Thursday, December 1, 2016 2:21 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] 1610 update not showing in console Thanks for the reply Sherry. It's been 2 days since the script was run. Still nothing. Was your lab running 1511 or something newer? My colleague has told me he's seeing a version check in one of the logs and thinks that's what is denying us access to 1610. So I am just trying to confirm that we, at 1511, cannot go directly to 1610. Erik On Thu, Dec 1, 2016 at 10:58 AM, Sherry Kissinger <[email protected]<mailto:[email protected]>> wrote: in my lab; after running the script; I noticed 1610 wasn't there right away either. I don't recall how long it was--I got distracted by production. by the time I got back to the lab it was the next day--and it was there. You may just need to wait longer? On Thu, Dec 1, 2016 at 12:23 PM, the codepoets <[email protected]<mailto:[email protected]>> wrote: We have 1511 installed and seemingly working fine in both our LAB and Production. I see 1602 and 1606 in both consoles, but not 1610. I know 1511 is stated as the minimum, but has anyone confirmed this and done an in console upgrade from 1511 to 1610? (And yes, I've already tried running the PowerShell script to make the update available with no luck. The script completes fine but there is no change in either environment) Thanks, Erik -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
