Home»Time Entries Audit loading ... [hide int notes] generated 8/8/2026 at 9:28:55 pm took 0.52 seconds version: b85cbb8 helpers: v1
Territory: BMS Month: « Jun 2026 » Company: all Ticket: all User: all Type: Remote [x] Role: all Bill: all Timesheet: all 6/1 6/8 6/15 6/22 6/29 Board: all Entry Status: all Ticket Status: all Issue: Notes longer than 500 characters [x] [reset] Progress: 100% (9 of 9)
| row | id | Terr | Company | User | Date | Day | Start | End | Actual | Billed | Deduct | Inv Amt | Work Type | Work Role | Bill | Timesheet | Board | Entry Status | Ticket Status | Ticket # | Ticket Summary | Int Notes | Audit Done | Audit Notes | Notes | # issues | all issues | errors | warnings | notices |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 41115 | BMS | OMNI | fdrewett | 6/3 | 7:30 am | 11:30 am | 4.00 | 4.00 | 0 | 500.00 | Remote | Standard Technician | Billable | 6/1 | Help Desk 2.1 | Billed | -Closed | 76486 | AMR SERVER DOWN | 1 | 7/26 CS long notes ok | **omni-docker01 MySQL crash incident - RESOLVED 11:36 AM** Production MySQL on omni-docker01 \(Omni POS at the AMR location\) entered a crash loop after this morning's automatic update bumped MySQL from 8.4.8 to 8.4.9. Omni POS and menu services were unavailable from approximately 07:57 until 11:36. Root cause: the MySQL config referenced an orphaned encryption keyring plugin left over from a July 2025 install. The new 8.4.9 binary failed to load that stale plugin and crashed on startup before reaching the database. After five failed restarts, the service gave up. Because the server uses encryption at rest, the obvious quick fix \(removing the bad config line\) would have made the encrypted data unreadable. Identified the correct path instead: migrating to MySQL's supported replacement keyring component, which uses the same on-disk format so no data loss or re-encryption is required. Engagement was read-only diagnostics on our side. Walked Kevin Adams \(Omni's server lead\) through the root cause and remediation plan. Kevin applied the migration during the incident, preserved all encrypted tables, and confirmed resolution at 11:36 AM. Also audited the server's automatic-update policy and found it would likely trigger the same class of failure on future updates. Drafted a configuration override to address that. Deliverables: full migration runbook, single-page remediation cheatsheet, and a self-contained incident writeup in the shared OMNI\_Docs vault for the Omni team. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 2 | 41462 | BMS | IC | fdrewett | 6/16 | 2:00 pm | 3:00 pm | 1.00 | 1.00 | 0 | 125.00 | Remote | Standard Technician | Billable | 6/15 | Help Desk 2.1 | Billed | -Closed | 77032 | Lisa - Access to Ninja and Teams Messaging to insighnm.com | 1 | 7/26 CS long notes ok | Call with Lisa McClaren ∙ Frank Drewett answered June 16, 2026, 3:00 PM Call summary ∙ Lisa is trying to regain access to Ninja but has not received a response to her help request. ∙ Frank is troubleshooting Lisa's access issues and decides to resend the invitation to Ninja. ∙ Lisa needs to be able to use Teams with Amanda but is currently unable to call anyone at Insight through Teams due to email disconnection. ∙ They discuss settings related to Microsoft Teams and external communication limitations between their organizations. ∙ Frank suspects that Lisa's domain needs to be whitelisted to enable communication with Insight users. ∙ Frank agrees to reach out to Damien for confirmation on the necessary settings and whitelisting. Next steps ∙ Frank will resend the invitation for Ninja access to Lisa. - Done - She has access to Ninja. ∙ Frank will check the settings for Teams communication and whitelisting for Lisa's domain. - From what I can see, there are no restrictions for external communications between Teams tenants. ∙ Lisa will send an email to Damien to request confirmation on the changes needed for Ninja Access ∙ Frank is waiting on Damien to verify Lisa's access to all the machines in Ninja | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 3 | 41776 | BMS | NMLGL | mleasure | 6/24 | 1:32 pm | 2:20 pm | 0.80 | 1.00 | 0 | 125.00 | Remote | Standard Technician | Billable | 6/22 | Help Desk 2.1 | Billed | -Closed | 77324 | Intern adobe account | 1 | 7/26 CS long notes ok | Created ITGlue documentation for deployment of custom Adobe Acrobat exhibit stamps using the provided Exhibit-Stamp.pdf file. Documented the per-user stamp install path at %AppData%\\\\Adobe\\\\Acrobat\\\\DC\\\\Stamps\\\\ . Installed/configured the exhibit stamp PDF for 2 users by placing the stamp file in each user’s Acrobat Stamps folder and verifying Acrobat could access the custom stamp set after relaunch. Also added/assigned the required Adobe licensing for both users in Adobe Admin as part of setup so Acrobat stamping functionality would be available under their accounts. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 4 | 40839 | BMS | HH | rclingan | 6/1 | 8:05 am | 11:06 am | 3.02 | 3.25 | 0 | 406.25 | Remote | Standard Technician | Billable | 6/1 | Help Desk 2.1 | BilledAgreement | -Closed | 76402 | Intune Setup for android phones | 1 | 7/26 CS long notes ok | Reviewed requirements for migrating Heading Home's ~45 Google Pixel phones from ManageEngine MDM to Microsoft Intune. Confirmed strategy: fully managed Android Enterprise (COBO) enrollment, with migration staged as a follow-on project after GWS cutover stabilizes. Created a dedicated Gmail account (headinghomeaebind@gmail.com) for Managed Google Play binding — kept separate from the GWS tenant to avoid lifecycle dependency. Bound Android Enterprise to the Heading Home Intune tenant via Managed Google Play. Resolved an authentication issue during binding caused by mixed browser sessions between MSP and client tenant — completed successfully by running the full flow in a clean InPrivate session authenticated to the Heading Home tenant. MGP connector status confirmed as Active. Created a Fully Managed enrollment profile named "Heading Home - Android Fully Managed" with device naming template HH-AND-{{SERIAL}}. Created a static Entra security group "Heading Home - Android Enrollment" and added Intune Provisioning Client as owner to satisfy enrollment profile requirements. Created a dynamic Entra security group "Heading Home - Android Devices" (rule: device.deviceOSType -eq "Android") for policy targeting. Approved and synced M365 apps via Managed Google Play (Outlook, Teams, Edge, OneDrive, Authenticator, Intune Company Portal, Zoom, ADP). | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 5 | 40840 | BMS | HH | rclingan | 6/1 | 11:21 am | 1:00 pm | 1.65 | 1.75 | 0 | 218.75 | Remote | Standard Technician | Billable | 6/1 | Help Desk 2.1 | BilledAgreement | -Closed | 76402 | Intune Setup for android phones | 1 | 7/26 CS long notes ok | Assigned all apps as Required to the Android Devices group. Created Android Enterprise compliance policy (Fully Managed) with numeric complex PIN, 15-minute inactivity lock, encryption required, and rooted device blocking. Created device restriction profile with key de-Googling settings: blocked personal Google accounts, blocked factory reset by user, blocked unknown app sources, blocked Play Store open access, set automatic system updates, configured FRP recovery email to bms@headinghome.org. Completed a successful test enrollment on one Pixel device — all policies applied and apps pushed successfully. Noted that Google Workspace accounts can still be added to devices (work accounts only, not personal), which will be resolved once GWS accounts are suspended as part of the ongoing migration. CA policy requiring device compliance intentionally deferred until full fleet migration is complete. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 6 | 41357 | BMS | IC | rclingan | 6/9 | 8:30 am | 2:30 pm | 6.00 | 6.00 | 0 | 750.00 | Remote | Standard Technician | Billable | 6/8 | Help Desk 2.1 | Billed | -Closed | 76963 | Damian Continued issues with email | 1 | 7/26 CS long notes ok | Troubleshoot issues with damian emails. 95gb in mailbox currently, 80gb in in-place archive 175gb total. owa and current desktop application are both trying to sync over 75gb of mail each time they load. this is causing major issues. Set archive policy down to 1 year from 2 years. begin autoarchive in background via powershell rebuild outlook desktop profile while only syncing 6 months of mail. Verify all mail syncs down and double check performance of email. mail sending and receiving as expected now - outlook opens in a reasonable time period need to double check the status of archive in a few days. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 7 | 42019 | BMS | HH | rclingan | 6/23 | 10:00 am | 12:00 pm | 2.00 | 2.00 | 0 | 250.00 | Remote | Standard Technician | Billable | 6/22 | Help Desk 2.1 | BilledAgreement | -Closed | 78812 | Shared calendar and teams chat troubleshooting | 1 | 7/26 CS long notes ok | Investigated request to remove duplicate Teams group chat via admin center; confirmed architectural limitation (group chats live in participant mailboxes, no central admin object to delete) and recommended rename/redirect workaround to consolidate users back into the proper M365 Group channel. Clarified calendar delegation behavior (per-user, on by default, no admin config required). Troubleshot shared calendar access issue for less-technical staff — traced root cause to calendar being hosted as a secondary calendar in a non-interactive service account mailbox (no native users), making it inaccessible for frictionless editing. Evaluated and ruled out OWA deeplink workaround (no supported parameter for targeting a specific shared calendar). Recommended migrating the calendar to an M365 Group/Team with a Channel Calendar tab to eliminate per-user permissioning and provide a native event-entry point. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 8 | 41798 | BMS | SVC | rclingan | 6/25 | 10:00 am | 10:30 am | 0.50 | 0.50 | 0 | 62.50 | Remote | Standard Technician | Billable | 6/22 | Help Desk 2.1 | Billed | -Closed | 77367 | Fix 5064 crystal pm issue | 1 | 7/26 CS long notes ok | **Issue:** Crystal PM \(Crystal.exe\) threw an unhandled exception when navigating to the patient page. Error: System.IO.FileLoadException — "An Application Control policy has blocked this file" \(HRESULT 0x800711C7\) on CNI\_SelectableItem.dll. **Root cause:** Windows Smart App Control \(SAC\) was enforced on this Win11 Pro workstation and blocked the unsigned Crystal DLL. Confirmed via CodeIntegrity event 3077 citing policy ID 0283ac0f-fff1-49ae-ada1-8a933130cad6 \(VerifiedAndReputableDesktop = SAC enforced\). DLL loads lazily on the patient page, which is why the app launched but crashed on chart open. SAC has no per-app/path exception, so it had to be disabled. **Resolution:** Set HKLM:\\SYSTEM\\CurrentControlSet\\Control\\CI\\Policy\\VerifiedAndReputablePolicyState = 0 \(elevated\), rebooted. Crystal now loads the patient page normally. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters | ||||
| 9 | 41821 | BMS | MEC | rclingan | 6/25 | 2:15 pm | 2:45 pm | 0.50 | 0.50 | 0 | 62.50 | Remote | Standard Technician | Billable | 6/22 | Help Desk 2.1 | Billed | -Closed | 77373 | a-4819 crashing | 1 | 7/26 CS long notes ok | **Ticket Summary — Lenovo Ultra 9 285 \(Arrow Lake\) BSOD** **Symptom:** BSOD CLOCK\_WATCHDOG\_TIMEOUT \(0x101\) observed 6/25, stuck at 0% \(dump failed to write\). **Investigation:** Event log review showed mixed crash history, not a single fault type: * 6/8 & 6/10: 0x116 VIDEO\_TDR\_FAILURE \(dumps written\) — GPU fault * 6/16 & 6/25: Event 41 + 6008, no dump — dumpless hangs \(incl. today's 0x101\) * WHEA-Logger: all entries ID 3 / Informational only — **no CPU machine-check errors**, so no evidence of failing CPU silicon. **Root cause \(probable\):** GPU = Arrow Lake integrated Xe \(iGPU\), so the TDRs and the watchdog timeout are the same package. Out-of-date Intel graphics driver identified as primary culprit. No hardware fault indicated. **Action taken:** Updated Intel iGPU graphics driver, and all other drivers. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters |
Legend:
(hover over fields for details)
Tickets with over 5 hours in the current view (2)
| Hours | Ticket # | Company | Ticket Summary |
|---|---|---|---|
| 6.25 | 76402 | HH | Intune Setup for android phones |
| 6.00 | 76963 | IC | Damian Continued issues with email |
Notices
| Field | Message | Count |
|---|---|---|
| Notes | Notes longer than 500 characters | 9 |
| Total | 9 | |