I don’t have a lab environment, so would you recommend running the script in production, or will the update show up at a later date for those that don’t run the script?
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Sherry Kissinger Sent: Thursday, December 01, 2016 10:59 AM To: mssms@lists.myitforum.com Subject: Re: [mssms] 1610 update not showing in console 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 <thecodepo...@gmail.com<mailto:thecodepo...@gmail.com>> 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
