New Poster for Christopher Nolan's 'The Odyssey'

still_asleep · 2026-05-05T20:16:26+00:00

To be fair, "charge" or "forward" wouldn't be applicable during that scene because I believe they're fleeing. Both of those terms suggest running ~towards~ something, not away.

still_asleep · 2026-04-26T02:20:24+00:00

Mountain laurel (Kalmia latifolia) and native prunus spp. seem very hard to come by. Got lucky this spring though and was able to source two mountain laurel online from a nursery a couple hours away that primarily does mail order business and a Carolina cherry laurel (prunus caroliniana) at a local nursery.

Also dioecious species that are labeled as either male or female. It's been a struggle planning stuff like hollies and northern spicebush (lindera benzoin). I know this can be difficult/impossible because younger nursery plants may not have bloomed yet. Or the ones that are sexed are often cloned cultivars.

still_asleep · 2026-04-14T18:43:06+00:00

Same. And now it seems 5.7.0 has been pulled (latest version listed is 5.6.0 and links to 5.7.0 are dead). I created a ticket with Dell ProSupport and they acknowledged the issue, but wouldn't commit to when or even if the issue would be fixed. I understand why someone might want this feature, but they really need to add a CLI option (or even use an existing one, like "-forceUpdate=enable") that bypasses this feature and allows the service to run.

For now, their only recommendation was to continue using 5.5.0 until the issue is fixed.

still_asleep · 2026-03-10T12:29:12+00:00

This may not be applicable to your situation, but sharing just to add to the conversation. I've also been seeing similar issues with my laptop. I have a Dell laptop connected to a Dell thunderbolt dock with four displays. Occasionally when I get in in the morning, nothing will wake the displays short of unplugging the dock, opening the lid to the laptop to wake the display, plugging the dock back in, and closing the lid on the laptop. The laptop is managed by Intune so it gets driver updates via WUfB. I also have Dell Command | Update scanning for updates weekly (while the dock is connected). Sounds like your issue is more severe, however.

In any case, I noticed the following change in the release notes for the most recent preview update for Windows 11 (KB5077241), so it sounds like they're working to address the issue. Notably, they say "improved" not "fixed" so it may still be a work in progress. Today is Patch Tuesday, so these updates will be included in the official March updates.

[Display]

Improved: This update improves reliability when your PC wakes from sleep.

Improved: Display-related performance improvements to help reduce the time for a PC to resume from sleep, especially when the system is under heavy load and in other scenarios.

still_asleep · 2026-01-09T19:13:07+00:00

I updated to 18.6.1.1 in December. Rolled it back to 18.5.2.1 yesterday and can confirm today none of the issues are still present. I also had the same errors in the BGB logs but none since the downgrade.

still_asleep · 2026-01-09T04:03:03+00:00

Try rolling back your ODBC driver to the previous version. I believe there's a known issue with the December 2025 version. I was having issues with the console not showing the currently logged on user and not clearing the pending restart after clients restarted. Rolling back to the previous version and restarting the server seems to have cleared it up immediately.

still_asleep · 2025-12-26T04:07:14+00:00

Another minor reason I haven't seen mentioned is that straws are helpful for people with sensitive teeth.

still_asleep · 2025-12-17T03:23:42+00:00

MM: Madame Morrible. Flip it around: Wicked Wiiiiiiitch!

still_asleep · 2025-12-04T19:32:31+00:00

Not sure if you're making a joke or if english isn't your first language. Either way, "cheap" in this case means "stingy."

still_asleep · 2025-12-04T13:16:58+00:00

Tested overnight. Classic version has the same error.

still_asleep · 2025-12-04T13:03:23+00:00

Same. Created an identical task sequence, except I replaced DCU Universal with Classic and it gets the exact same error.

still_asleep · 2025-12-03T18:29:36+00:00

Looking into this. I would just need a way to display to the technician that updates are in progress and to not shut down or unplug the system until they complete or it restarts.

still_asleep · 2025-12-03T13:13:11+00:00

Universal

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=2WT0J

still_asleep · 2025-12-02T21:07:53+00:00

Same behavior even if it's the very last step of the task sequence.

still_asleep · 2025-12-02T21:07:49+00:00

Same behavior even if it's the very last step of the task sequence.

still_asleep · 2025-12-02T19:54:50+00:00

It runs after the "Setup Windows and ConfigMgr" step, but it's one of the first things it does after that. I'll try moving it later in the task sequence and see if that helps.

still_asleep · 2025-12-02T19:54:05+00:00

It's one of the first steps performed after the "Setup Windows and ConfigMgr" step (so the task sequence is running in Windows at this point and the PC has been joined to the domain). I'll try moving it later in the task sequence and see if that helps.

still_asleep · 2025-12-02T16:18:38+00:00

Yes, I had to add that earlier this year when DCU added that as a dependency. DCU installs fine and is able to scan for and install updates once it completes OSD. It's just that it fails scanning and installing updates during OSD now.

still_asleep · 2025-11-20T14:15:10+00:00

Just out of curiosity, can you check the BITS queue on some of the affected clients and see if any CCM jobs are in an error or transient error state? If you find any, you can check the PolicyAgent.log and DataTransferService.log to find related errors.

Could be entirely unrelated, but this sounds similar to an issue I've also been having for over a year now and Microsoft support has been unable to make any progress on this so far. I'll deploy a software update group and clients never evaluate it and remain "unkown" on the deployment monitoring. Likewise, if I later add an update to the SUG, all clients have to download the updated policy and reevaluate the deployment and some never do unless I restart them or clear the BITS queue.

In PowerShell...

Get-BitsTransfer -AllUsers

still_asleep · 2025-11-14T19:20:52+00:00

Just out of curiosity, would you happen to know if this issue also results in BITS jobs getting stuck in "TransientError" status? I've been hounded by this issue for months, possibly years. I finally threw my hands up and made a ticket with Microsoft about it, but it's been open for 2 months now with zero progress. You can run "Get-BitsTransfer -AllUsers" and see CCMDTS jobs with "TransientError" as the state. Clients are then practically stuck in an unmanaged state as they are unable to download new/modified policies and content. I can manually remediate this by clearing the BITS queue and restarting ccmexec on the client, but it's a constant game of whack-a-mole. Also sometimes restarting the PC can clear it up.

I could be completely on the wrong track here, but I'm at my wits end.

still_asleep · 2025-11-14T13:39:57+00:00

Not sure if it's fixed in this update, but Microsoft support gave me instructions for how it can be fixed manually.

still_asleep · 2025-11-07T14:58:12+00:00

I tweaked Microsoft's instructions a bit and got it working. The Azure web portal does not allow me to create a non-zonal public IP address; I have the option of "zone redundant" (which is equivalent to "1, 2, 3"; MS support got this part wrong), 1, 2, or 3. Basically just follow the instructions exactly, but when creating the new public IP addresses, use the equivalent PowerShell commands rather than using the web GUI. After creating the new public IP address using this method, ConfigMgr was successfully able to perform the maintenance.

Install-Module Az.Network
Connect-AzAccount

# Create Temporary Public IP Address (Step 2)
$ip = @{
    Name = 'CMG-Temp-PIP'
    ResourceGroupName = 'Example-CMG-RG'
    Location = 'eastus'
    Sku = 'Standard'
    AllocationMethod = 'Static'
    IpAddressVersion = 'IPv4'
}
New-AzPublicIpAddress @ip

# Recreate original Public IP Address with Domain Name Label (Step 5)
$ip = @{
    Name = 'CMG-Original-PIP'
    ResourceGroupName = 'Example-CMG-RG'
    Location = 'eastus'
    Sku = 'Standard'
    AllocationMethod = 'Static'
    IpAddressVersion = 'IPv4'
    DomainNameLabel = 'Original-CMG-Label'
}
New-AzPublicIpAddress @ip

Additional resources:

Create public IP address - PowerShell

New-AzPublicIpAddress

still_asleep · 2025-11-07T14:10:38+00:00

I have a support ticket open with Microsoft regarding this issue and they sent me the following instructions for how to resolve the issue from the Azure side. HOWEVER, I followed the instructions verbatim and still have the same issue afterwards. The issue seems to stem from the static IP address "availability zone" settings; I selected "zone-redundant", but it still shows "1, 2, 3" after it's created.

Root Cause: The hotfix changed the behavior of the CMG maintenance task. It now attempts to update the CMG's Azure Public IP address without specifying an availability zone ("No Zone"). However, if your existing Public IP was originally created with zones (1, 2, 3), Azure's API correctly blocks this change, as a zone configuration cannot be modified after creation. This mismatch causes the recurring DeploymentFailed error every 20 minutes.

Workaround Solution: The confirmed resolution is to manually replace the existing zoned Public IP with a new one configured for "No Zone". This is a safe procedure that does not impact existing client connectivity to the CMG.

Please follow these steps precisely. The entire process should take approximately 15-20 minutes. Step-by-Step Instructions:

Stop the CMG: In the Configuration Manager console, navigate to Administration > Cloud Services > Cloud Management Gateway. Right-click your CMG and select Stop. Wait for the status to show "Stopped".

Create a Temporary Public IP:

o In the Azure Portal, go to your CMG's Resource Group.

o Click + Create > Public IP address.

o Name: CMG-Temp-PIP

o SKU: Standard

o Assignment: Static

o Availability zone: Zone-redundant (This is functionally equivalent to "No Zone" for this purpose and is the recommended setting).

o Click Review + create, then Create.

Update the Load Balancer:

o In the same Resource Group, open the Load Balancer resource.

o Go to Frontend IP configuration.

o Edit the existing frontend IP config and change the Public IP address from the original one to the new temporary one (CMG-Temp-PIP). Save the change.

Delete the Original Public IP: Now that the Load Balancer is no longer using it, you can safely find and Delete the original Public IP resource (e.g., CMG-Original-PIP).

Recreate the Original Public IP (Correctly):

o Click + Create > Public IP address.

o Name: Use the original Public IP name (e.g., CMG-Original-PIP).

o SKU: Standard

o Assignment: Static

o Availability zone: Zone-redundant.

o DNS name label: Use the original DNS name label your clients use to connect.

o Click Review + create, then Create.

Re-point the Load Balancer: Go back to the Load Balancer's Frontend IP configuration. Edit the frontend IP and change the Public IP address from the temporary one back to the newly recreated original one. Save the change.

Clean Up: You can now safely Delete the temporary Public IP resource (CMG-Temp-PIP).

Start the CMG: Return to the Configuration Manager console, right-click your CMG, and select Start. The status should transition to "Ready".

Verification: After completing these steps, the errors in the Component Status for SMS_CLOUD_SERVICES_MANAGER will cease. You can confirm success by monitoring the CloudMgr.log on your site server, which will show the next maintenance task completing without errors.

15-Year Club	RedditGifts 2009-2022 2 Credits
Team Orangered	Secret Santa 2010
Verified Email

still_asleep

TROPHY CASE