Underneath my monitor, there is a pile of ID's. Take a look at the link here and verify if we have these ID's.

As we discussed, we should expand our plan so that we cover all the rooms that REACH will be in first so that those rooms have the new Phones. Let's add it here

As always, we will continue to tackle assets missing data. Make sure every field that is missing (and that applies) is accounted for. If you have any questions with anything, please let me know.

Let's go over a few tickets that I would like to catch up on that require one of you to check onsite. Check them out in the WHD first:

1. 36386
2. 36098
3. 36294
4. 35952
5. 36162

Let's review this today and make any changes to the plan/doc here

As always, we will continue to tackle assets missing data. Make sure every field that is missing (and that applies) is accounted for. If you have any questions with anything, please let me know.

Let's go over a few tickets that I would like to catch up on that require one of you to check onsite. Check them out in the WHD first:

1. 36386
2. 36098
3. 36294
4. 35942
5. 36162

Mr. Machuca and I now expanded the scope and all Poly Phones have reserved IP addresses. I have updated this in the Web Help Desk to reflect this change. So, let's continue to connect/ provision these phones. As you are connecting the phones, confirm the IP address by referencing the Help Desk using the asset tag number. FYI, all poly phones contain the 10.10.1.x address.

As always, we will continue to tackle assets missing data. Make sure every field that is missing (and that applies) is accounted for. If you have any questions with anything, please let me know.

LCR PC​

I will send an invite for us to look at the LCR PC together and make some space.

TBD

Let's meet to talk a little more about the plan to about sunsetting our current Cisco phones. Look out for a Zoom invite.

As an FYI, here is what Vincent set up as a plan so far:

Hi everyone,

Here is a draft of the plan for the rollout of our new Zoom phones:

Swap-Out Process: The physical transition is straightforward. We are simply unplugging the old Cisco phones and plugging in the new Poly phones with the old Ethernet cable. No new cables are required.

Logistics & Disposal: Because the old Cisco phones do not fit into the new Poly packaging boxes, we have set up the following collection process:

• Floor-by-Floor Collection: Our interns will move floor-by-floor with a moving cart in the hallway to collect the old Cisco phones as they are removed.
• Storage: After completing each floor, the interns will return the cart to the IT Office (Room 212) to unload the old phones.

Staff who can't be at their offices: For teachers and staff not able to be at their offices due to the construction:

• Your new Poly phone will be temporarily set up at your current, temporary location.
• Once construction finishes, the phones will be moved to the teachers' permanent location. We estimate this second part will take place around the middle of August. `

As always, we will continue to tackle assets missing data. Make sure every field that is missing (and that applies) is accounted for. If you have any questions with anything, please let me know.

TBD

Mr. Machuca and I confirmed that we would expand the scope pool. With that said, I am in the process of reserving IP addresses for all our Poly phones. Be on the lookout for notice from me and/or Mr. Machuca once those addresses are set in place. Then, we can continue to connect and provision these phones. (Note: we are setting two common are phones aside so that we may test a solution to our root cause with ZTP).

Let's continue to provision these phones. We can keep connecting user phones and start on Common Area Phones as well. I've cleared most addresses in the dynamic address pool.

Let's continue to tackle auditing and acknowledging these assets making sure we get the correct missing info.

Please read what Shawn at TCS stated:

in doing some more research, it appears that because the devices came from different vendors (listed in the email Jeffrey sent) that the firmware version ambiguity is most likely the issue.

Why ZTP Isn't Working — Firmware Ambiguity Across Vendors​

Your three vendors shipped units carrying whatever firmware happened to be loaded at manufacture — ranging from 8.0.x (older) up to 8.6.0 (current). That firmware version is the deciding factor, not the phone itself:

• PVOS 8.0.x and earlier: local admin password is the static industry-standard default (456), with no forced change. ZTP runs uninterrupted straight through to Zoom.
• PVOS 8.5.0 and later: Poly enforces California's IoT security law (SB-327), which prohibits a device from operating on a known default password indefinitely. On these builds, the phone halts on first boot and forces an admin password change before allowing anything else to proceed — including the ZTP handshake to Zoom. That local gate is what's stalling these units, not a Zoom-side or network problem.

Bottom line: phones on older factory firmware auto-provision cleanly; phones on 8.5.0+ stall at the password gate until someone clears it. Mixed vendors = mixed firmware = mixed results, all on the same network.

Forcing Provisioning / Reset Path​

For any stalled phone:

• Check firmware first (phone screen: Settings → Status → About, or the web UI Home tab).
• If firmware ≥ 8.5.0 (or already upgraded): the phone will stop at the password screen — that's not avoidable. Clear it:
  • Enter 456 as the current/old password.
  • Enter your standardized org password as the new password (same one every time — don't let it vary by tech).
  • Continue through the remaining setup screens.
• Once past the password gate, force config delivery instead of waiting on ZTP redirect:
  • Manually set Provisioning Server Address to Zoom's provisioning URL, or
  • Better at scale: point your DHCP option (66/160) at Zoom's Poly-specific provisioning URL — https://provpp.zoom.us/api/v2/pbx/provisioning/polycom. Every phone on that subnet picks this up on boot without depending on Poly's ZTP redirect server at all.
• Confirm the device shows Online/Registered in Zoom Admin Console.
• If a phone is locked out with an unknown password: use the factory reset sequence you already have (unplug/replug → Cancel → hold 6+8+* → try 456/789/MAC-no-dashes). Know going in: this resets config, not firmware — it'll land right back on the same forced password screen on 8.5.0+ units. Don't treat repeated resets as a routine fallback; there are scattered reports of Edge E-series units getting into a bad state after repeated reset/reprovision cycles, so if one reset doesn't resolve it, escalate rather than keep cycling it.

In my honest opinion, this isn't exactly what we've seen, especially with phones that have the 8.0.xxx firmware version we have seen that this

"PVOS 8.0.x and earlier: local admin password is the static industry-standard default (456), with no forced change. ZTP runs uninterrupted straight through to Zoom." and this "Bottom line: phones on older factory firmware auto-provision cleanly; phones on 8.5.0+ stall at the password gate until someone clears it. Mixed vendors = mixed firmware = mixed results, all on the same network." is not entirely accurate. It is actually the opposite - phones on 8.0.x stall at the password gate until someone clears it.

With this being said, Dominic I like your thinking which is restated there by Shawn. Good work.

So now, we can attempt to have our DHCP server do the work of having it point the Zoom phone to the provisioning URL. I created a DHCP reservation for one phone as a test (Christine Badi) and set 066 configure option to the provisioning url. Let's start with hers, see what results we get, and move forward.

Please continue to provision the Zoom phones. As we discussed, when connecting a Zoom phone and you see it is stuck in the menu where it is asking for an admin password, insert "123", access its web interface, and manually insert the provision URL: https://provpp.zoom.us/api/v2/pbx/provisioning/Polycom/edge-e220. Then, wait for provisioning to begin.

We should revisit this ticket (ticket # 36567). I would like to get a little more context and try to have this solved today.

Please continue to work on laptop asset imports by filling out the template - which you can access here if needed.

Once you've filled it out, please send it to me and copy Mr. Machuca and Mr. McKee via email so that we may review it and perform an import.

Please continue to look at the "Assets Missing Data" and update a few assets a day.

Reminder: You all now have access to the WHD Reports here.

I believe you all started on this yesterday and made progress. Thank you for doing so. Continue to finish up work here. As I mentioned there are certain fields that are required to be filled out, along with others than concern us (MAC & WiFi MAC, serial number, etc). You may also refer to other Asset Type: Laptops in WHD to see what other fields were filled for laptops.

• Download the template linked here.

Once you've filled it out, please send it to me and copy Mr. Machuca and Mr. McKee via email so that we may review it and perform an import.

As mentioned, these are reports that are pulled from the Intranet that highlight any incorrect or missing field data for specific assets. I am currently working with Mr. Croce to give you access to those reports in the Intranet, so look out for that. Once you do, we can start focusing on Assets Missing Data.

Update: Thanks to Mr. Croce, you all now have access to the WHD Reports here.

During the summer, we like to take advantage and perform A/V maintenance on projectors and other equipment in classrooms, conference rooms, and the auditorium.

A/V maintenance consists of cleaning out filters, testing all A/V connections, etc. We usually create tickets to track each room separately that lists all the A/V equipment that pertains to that room. Once these tickets are created, you may start to slowly chip away at them. Mr. Machuca and I will work on creating these bulk tickets. To give you and example, you can refer to ticket 34147 in WHD, or go to Tickets > Advanced Search > Subject : Contains : "Summer AV maintenance"

With help from Mr. Machuca, let's make sure we get the scanner connected to a machine. This will be helpful in getting correct info straight from the barcodes on the laptop boxes.

Continue with any work leftover from yesterday. Let us know if you have any questions.

The Raspberry Pi's in the basement IDF are to be audited in advance for the Regis Summer Institute. To access the IDF, you will need the D4 key. I have left my red lanyard with that key on my desk.

The Pi's are in that box that I showed you both last week. Remember, in that box there are the kits and the Pi's themselves. The Pi's are assetized. What you need to do are assign each of those Pi's to vbowman in the Help Desk and audit them along with the location.

Additionally, for Mr. Bowman, there needs to be a correct account of equipment that lives in those boxes. You may refer to ticket #36182 with more details. Here is a blurb below:

Just a quick question regarding the Summer Institute beginning in early July. I wanted to check that all Raspberry Pi kits are fully intact and accounted for. Since student enrollment has increased this year, we will likely need one additional kit, bringing the total to 11 kits.
Below is the updated list of engineering needs compiled with input from our instructors. 
Some items may already be available within your department, while others may need to be ordered.

1. Raspberry Pi Kits
- 11 Raspberry Pi kits
- 11 Raspberry Pi 4 Model B units
- 11 power supplies
2. IT Equipment (Room TBD)
- 11 monitors
- 11 keyboards
- 11 mice
3. Room with projector 

After this, make sure to bring it up to the IT office.

The laptops in Mr.Mckee's office are to be moved to room 410. Remember, there is informally a way that the laptops are organized on top of the cabinets. A few things to note:

• The last column on the left are to be carefully distinguished and set aside from the rest of the laptops - fyi, these laptops are high performance versions of the laptops teachers are getting.
• There is one laptop named "Marta". This laptop is for Dr. Baldassari. This is also a unique high performance version of the same model laptop.

Before you move anything, make sure to setup the space where the chairs are set aside in one corner of the room.

I believe, for now, the desks will be the where we will open up the laptops and label them. I believe this a question you may ask Mr. McKee or Mr. Machuca. Otherwise, we will need a foldable table that the Facilities team may provide.

In 410, it may helpful to bring a few surge protectors which can be found in the IT Office Head End Room. That way we are prepared once we start opening up these laptops and connect them to power.

There are some boxes of items that have been brought down from Joe DeLesseio's office from Advancement. You may go through them. Make sure to compare any assets assigned to jdelessio in the Help Desk (you can use the desktop or laptop there and sign in into the Help Desk) and see if there ay assets in the box there that belong to him. Make sure to audit and change the asset location.