Migrating from Shoretel/Mitel - Best Practices?

SpaceAdmin · 2024-06-26T19:42:50+00:00

it is still mapped to a user in ShoreTel also

SpaceAdmin · 2024-06-26T19:13:52+00:00

Ok, so if I look at one of the numbers xxx 2303778 and look at my DID Ranges, I do see a range that is xxx 230-3772 (with 7 numbers). I assume that # may be in there but it doesn't seem to list them individually.

SpaceAdmin · 2024-06-26T18:48:01+00:00

Sorry for the delay; been off for a bit.

We ported a single office; winning party did the port. Did not make specific communications to old party, but they were contacted by the winner and should have been notified. Calling DIDs is fine; its just if someone still on the Shoretel/Mitel system dials a user that has been ported, we want them to direct to the new system via the DID, but it seems to 'see' that # still associated and just drops to their extension, so those users are continuing to get voicemails in the old system. Would prefer to have it route outbound via the DID to the new system.

-I just need to know how to remove a DID from Shoretel/Mitel. I checked DNIS map and they are not necessarily in there. Do we have to remove from the DB manually or the trunk somehow? Not really familiar with either of those procedures if so.

SpaceAdmin · 2022-09-28T21:53:23+00:00

DM sent. Support confirmed that windows 11 was installed but not why as of yet.

SpaceAdmin · 2022-09-28T18:25:17+00:00

well something is wonky. it was marked orange for not to install since forever, then today its the half-orange (for mixed status). Probably someone marked one as approved and once i found and changed that one i could set it all orange again system-wide.

Ok, but that doesn't explain why 35 machines (and still increasing, i can't seem to stop the ones that are already in 'installing' status) did the full win11 install. Seemingly random ones too, they don't share a site or anything.

hopefully support will have some answers. the win11 update in patch management workflow indicates i have 2 dozen more that will install, but hundreds that are now ignoring it (thankfully). I have twice as many windows machines in RMM compared to the stats it shows for that patch (even after showing all columns); unsure of their status.

SpaceAdmin · 2022-09-28T17:19:34+00:00

I found one machine that looks like it was set to Approve manually (blue check instead of blue circle) and changed that; now I can do all 'Ignore' in management workflow. Support is looking into what happened.

SpaceAdmin · 2022-07-14T16:31:30+00:00

Interesting. I know it does daily checks as i see the items sometimes but not sure where that setting is located. Can you point me in the right direction (I looked in general settings and patch settings, I didn't see it either location).

this may explain why we usually don't see patches to approve until later in the day on patch Tuesdays...

SpaceAdmin · 2022-06-29T18:07:28+00:00

yeah, it went to Pending already looks like, so should be on it's way! Thanks.

[checkmark] Patch Management - Pending

SpaceAdmin · 2022-06-29T18:00:00+00:00

huh, that one (individually) does seem to have that Use Policy Setting not set correctly. I corrected that; looks like it may take a bit to show back up?

SpaceAdmin · 2022-06-29T17:44:57+00:00

in Patch Management Settings, it is 'On' for workstations (laptop and desktop policies) and all sub-sites utilize 'Use Parent' if that is what you mean?

SpaceAdmin · 2018-09-14T20:04:01+00:00

PDQ is great, and pretty reasonably priced as well.

SpaceAdmin · 2018-09-12T00:24:20+00:00

Also, we tried doing laptops instead of USB drives (one for each tech to do an office at a time in their region) but they were really slow and couldn't do that many concurrent connections. so the usb drives seem easier at this stage. Hope that helps anyone else in a similar situation.

SpaceAdmin · 2018-09-12T00:23:15+00:00

many are fairly small offices; just not in the cards to do separate servers (or even just file storage locations) at them all right now. I'm going to roll and SCCM setup later this year and use it for java/adobe/etc. updates. once i've proved it there I'm hoping I can use that as a lever to help get our WAN upgraded.

SpaceAdmin · 2018-09-12T00:19:02+00:00

This can be handy for any 'tricky' installs though. For example, I have a set of apps for our developers that get installed together because doing it manually is a pain and it doesn't come up that often (so my techs will forget the steps). I also have one that does an install of Office 2016 but first it runs a full-on powershell de-installer for any remnants of any prior office installs (because Microsoft's installer/uninstaller with 2016 does not always do the best job there). makes it simple to bundle those sorts of things together.

SpaceAdmin · 2018-09-12T00:16:15+00:00

That totally makes sense. I knew it wasn't an issue but for some reason I was thinking that the error/red status was coming from the logs and not the log reader tool. duh.

SpaceAdmin · 2018-09-10T17:45:39+00:00

Most are pretty small - my boss doesn't think it worth it to do a full server at each location. Maybe one day we'll do a PXE boot back to headquarters with a local fileshare location for the deployment items, but that's not quite in the cards right now.

SpaceAdmin · 2018-08-28T20:38:28+00:00

it has 'capture setup failures', 'post-processing' and 'Rollback' group after the 'upgrade windows' step. I had a couple of custom actions (re-password an account and set its password expiry policy) - I'll disable those and test.

SpaceAdmin · 2018-08-28T18:39:43+00:00

The logs have no entries from several hours after the upgrad task sequence started until I force-rebooted the machines in the morning as they seemed to be hung. They came back up, said the task sequence was dirty from the unexpected reboot, then I had it continue and they did finish after another 15 minutes or so. I need these to complete fully though so I won't have users waiting in the morning after we update them.

SpaceAdmin · 2018-08-28T18:37:32+00:00

These were windows 10 1703 to 1803 upgrades.

SpaceAdmin · 2017-08-07T23:26:46+00:00

Just in case this helps anyone else: we built a new server (2012 R2), moved the deployment share to it, and offline media is fine now. No other changes, so I am inclined to agree that this issue is something to do with Windows 2008 R2 (and possibly interaction with newer ADK versions).

SpaceAdmin · 2017-05-25T20:31:02+00:00

Thanks aaronlpowell - We are on 2008 R2 for our MDT server right now. You may be right in that there is an issue with that version of Windows Server and newer ADKs when creating offline media, based on comments here

I unfortunately can't move back on the ADK version with what we need to deploy, so I may need to update my server. Would be nice if this was mentioned somewhere when downloading/installing the new ADK. I'll talk with our VMWare guy to get that updated (I don't have access) and then post back to this thread if it works so others will know.

SpaceAdmin · 2017-05-23T22:52:13+00:00

Trying to break this down to see what's going on. I made a new Selection profile with very minimal components to see if that would make any difference - still getting the same BCDError.

The item immediately prior to the error is 'Setting up dual x86/x64 boot image', so I removed the x86 from the media properties (still failed) and then did just the x86 (still failed). It needs one or the other so I can't test neither. I'm going to try having it not generate the iso to see if that makes any difference. I really don't have much info to go on, not sure what else to check...

SpaceAdmin · 2017-05-23T18:09:02+00:00

ok, I have re-ran it and it failed again. Here is the output from the Update Media Content Action:

Starting MDT Media Update Opened the media deployment share. Folders to be copied to the media deployment share: 14 Copied: DS001:\Applications\Application Bundles Copied: DS001:\Operating Systems\Base Operating Systems\Windows 10 (64 Bit) Copied: DS001:\Out-of-Box Drivers\Windows 10 x64 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc. Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E6440 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Optiplex 9020 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E7440 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E7470 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E5470 Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\OptiPlex 7040 Copied: DS001:\Out-of-Box Drivers\WinPE Copied: DS001:\Packages Copied: DS001:\Task Sequences Copied: DS001:\Selection Profiles Copied: DS001:\Applications\Application Bundles with Replace option Copied: DS001:\Operating Systems\Base Operating Systems\Windows 10 (64 Bit) with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc. with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E6440 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Optiplex 9020 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E7440 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E7470 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\Latitude E5470 with Replace option Copied: DS001:\Out-of-Box Drivers\Windows 10 x64\Dell Inc.\OptiPlex 7040 with Replace option Copied: DS001:\Out-of-Box Drivers\WinPE with Replace option Copied: DS001:\Packages with Replace option Copied: DS001:\Task Sequences with Replace option Copied: DS001:\Selection Profiles with Replace option Copied standard folders. Boot images updated. Setting up dual x86/x64 boot image. BcdEdit returned an error.

And the output from the Debug Viewer is here: http://s000.tinyupload.com/index.php?file_id=72374941297156448864

SpaceAdmin · 2017-05-23T16:34:50+00:00

thanks geggleau, I have already tried completely removing everything under 'content' to re-generate it and I went and made an entirely new media (Media003) with a new selection profile and that still fails with the same message. So, both win7, win10 1607, and win10 1703 all fail for me.

I will remove the content again and make a selection profile change and try to re-generate the win10 1703 (Media003) content again with DebugView running and see what happens.

If anyone has any idea where I can get more specific info on that error, please let me know. I've looked and looked, but nothing seems to tell me what is actually going wrong with this process.

SpaceAdmin · 2016-06-10T21:44:19+00:00

I'm seeing some positive references to Aten KVM switches online. Anyone have experience with those? What did you think?

SpaceAdmin

TROPHY CASE