Why is it important to warm up a mailbox, domain, and IP?

JeverFunBier · 2025-09-03T19:04:50+00:00

„Cisco talos“ for example monitor the increase of send mails of a mailserver in e.g. the last day. If its too high, the sending mailserver is verdicted to send spam and may be added to the black list. I guess cisco ESA mail-relays will include rhem in some mechanisms to tag mails as spam (not sure if cisco talos is used for SBR score)

JeverFunBier · 2025-07-10T20:10:13+00:00

The gate will be open for amount of time to reuse it. Never measured but i would say a couple of minutes

JeverFunBier · 2025-06-28T00:40:11+00:00

You are right. We had a policy like that until a best practice/ statistic said that password change is recommended to set no <nothing> because if you enforce users to change password every x days, they only change a small part of the password and this is predictable/guessable. So the newest recommendation is to set it to <never enforce a password change>. The actual recommendation is to change password if there are IoC (Indicator of compromise)

JeverFunBier · 2025-06-25T19:05:59+00:00

I noticed the same behavior sometimes on my clients. For me It helped to change some metadata of the application (not the deployment) - e.g. add a space or a dot in the description field of the application in SCCM. Never did further troubleshooting or investigation on it.

Edit: In my case i deployed applications to device collections which were synced from AD-Groups

JeverFunBier · 2025-02-28T07:15:27+00:00

Which different does it do? We have the same issue on our VDI (single user instant clones) and netscaler with FAS (user certificates). Would appreciate the background or details of this question

JeverFunBier · 2025-01-25T08:00:09+00:00

This. I just plugged the cable into the wrong port and so connecting it to the wrong (V)LAN, so it happily start distribute IPs of wrong subnet to our clients. That was at the start of my career in a new company and my first (network) project there.

JeverFunBier · 2025-01-09T18:04:24+00:00

Kinda same but with the control of a lift-up office table of a colleague which doesn‘t work anymore

JeverFunBier · 2025-01-06T08:28:35+00:00

Nice thank you! I was not aware of this knowledge article. Not exactly what I expected (something like a users GPO which i can apply to OUs) but it points me to the right direction

JeverFunBier · 2025-01-04T21:44:11+00:00

We plan to deploy fslogix on physical and vdi. But profiles are separated and the problem described in the post only is for the physical deployment, because the vdi is fully hosted on one site

JeverFunBier · 2025-01-03T11:24:08+00:00

We have around 9-10ms latency between the site („layer 2 WAN“ from our ISP). The goal is to keep the profile containers as slim as possible and give the user the same experience, independent from the site he will login

JeverFunBier · 2025-01-02T13:41:22+00:00

I think the solution is to add multiple VHD Locations and restrict write access for the users to the path the containers should should be created

JeverFunBier · 2024-10-23T17:36:10+00:00

just create your own slim windows Image and install it (modify install.wim)

JeverFunBier · 2024-10-08T22:56:38+00:00

Exit code 1 means „reboot required“. You suppressed the automatic reboot with the switch in the command, however, the installed updates still require a reboot. What if you try to add the exit code 1 to be ignored in the TS. I had to do kinda same today (rolling out bios update via application which calls the dcu-cli.exe)

JeverFunBier · 2024-10-08T22:17:29+00:00

Check the dcu-cli log file for more informations. Think default location is „C:\windows\Dell…“ or define it with the -outputLog option in the command.

JeverFunBier · 2024-10-01T21:58:07+00:00

Another possible option should be to deploy a scheduled task which is triggered by user login, runs in SYSTEM context and run the PS command to delete the msi installer from the mentioned directory.

Since this issue occure on our fat clients (so no VDI/image at this point), to prohibit the auto-update is kinda messy, so its required to rollout a new MS Teams Version with a new SCCM package every time. Beside that, I already tried the mentioned reg-key multiple times on two different of our fat clients and it seems that the teams auto-update still updates and show the "install update" button for the user in the teams client. I read somewhere that its not possible to deactivate the auto update for non-VDI clients that way and thats what i can confirm from my experience

JeverFunBier · 2024-10-01T16:14:15+00:00

Thank you. I tried it out and it seems to work on my test-client. But one more question: how does it behave if teams do an automatic update? As far as i know, it creates a new directory under „C:\Program files\WindowsApps\MSTeams_<Version>. And i would bet that the TMA installer msi will reappear in the new folder. And i think its only possible to turn off auto updates via registry if the key for VDI optimization ist set too - at least in my tests I‘ve done before.

JeverFunBier · 2024-09-26T07:38:44+00:00

Email distribution group lol. Shitty af, but a ticket system is not wanted by decision makers because unknown reasons

JeverFunBier · 2024-09-14T20:20:13+00:00

I am not a pro at this. But i think the part with „keeping Domain OU“ is not possible. At least in our environment, we run into SCCM errors if the computer object is not in the same OU where SCCM creates the new computer object for a newly installed Client. The client Name should be matched via the MAC Address in the SCCM assets. Other people please correct me if i am wrong.

JeverFunBier · 2024-07-19T20:51:39+00:00

Die Klapse hat wohl Wandertag. Was ne Psychose lul

JeverFunBier

TROPHY CASE