User Profile
StefanoC66
Iron Contributor
Joined 10 years ago
User Widgets
Recent Discussions
S2D FaultDomainAwareness
We're setting up a 2 Node windows 2025 cluster with storage spaces direct After creating the pool we created two virtual disk but see the following output PS C:\WINDOWS\system32> Get-VirtualDisk | Format-List FriendlyName, Size, FaultDomainAwareness FriendlyName : ClusterPerformanceHistory Size : 25769803776 FaultDomainAwareness : StorageScaleUnit FriendlyName : S2DVOL01 Size : 10995116277760 FaultDomainAwareness : FriendlyName : S2DVOL02 Size : 10995116277760 FaultDomainAwareness : The FaultDomainAwareness is empty for the two virtual disk created on the storage pool which is configured like this PS C:\WINDOWS\system32> Get-StoragePool –FriendlyName S2D-CLHV-001-Pool | Format-List FriendlyName, Size, FaultDomainAwarenessDefault FriendlyName : S2D-CLHV-001-Pool Size : 57592038555648 FaultDomainAwarenessDefault : StorageScaleUnit is there something wrong ?Hyper-v Virtual Switch warning
We have a four nodes Windows 2025 Hyper-v cluster with only one virtual switch of 2 NICS On each node we get this warning repeatedly V-Switch operation IOCTL_SWITCH_GET_INFO_EX (2241648) took too long to complete. Operation Type: IOCTL. Execution time 0 ms. Queued time 0 ms. Expected execution time less than 0 ms. SwitchName: CF06EC90-20EB-460D-9A88-6820BFCCB14D. SwitchFriendlyName: SWPrincipale Searching for it didn't get any useful thread so far, has anyone seen it and found the cause ? thanksHyper-v Replica Traffic segregation
We have two standalone Windows 2025 Hyper-v Servers. They have been configured with a network team for Management, one for VM traffic and one for replica traffic. We have configured both hosts with self-signed certificate to configure HTTPS replica. The two hosts FQDN are host1.company.com host2.company.com and those names are resolved in the DNS with the management Network IP. To have the replica going through the "replica team" we created on each host's host file two entry like host1.repl.company.com host2.repl.company.com pointing to the replica network IP. The self-signed certificate of each host contains both fqdn ( xxx.company.com, xxx.repl.company.com ) Problem is that when activating a replica for a VM if we chose xxx.repl.company.com as replication partner the process fails with the error that the hosts cannot be contacted, if we use the fqdn company.com it works. To test connectivity we also set the hosts file using the replica network IP for the company.com FQDN and it works. So it's like it doesn't like the FQDN repl.company.,com Any Idea on what the issue might be ? thanksDDG fields
We have Dynamic Distribution groups on On-prem which are using user's attribute as, an example, City and we should create the same DDG on Exchange Online. However we when creating the DDG from the Exchange Online Portal such attributes are not present. The only attributes shown are State/provice Company Department Custom1-custom15 Is there a way to have all the user's attributes available for creating DDG ?Re: OU list incomplete in AAD connect
LainRobertson Thanks for the input. I checked the missing OU's security settings and it has the inheritance enabled as the OU that I see. Checking the permissions they looked the same. The AdSync service is running as NT SERVICE\ADSync EDIT: even if apparently they have the same security settings applied "inherited" checking with "effective access" in the advanced tab for the "user" NETWORK SERVICE there's actually a difference that I couldn't understand coming from.Re: Local domain mailbox migration error
Dan_Snape that's correct, I know that it's the default policy managing the domain.local address and that I can remove it to solve the issue. My point is that in all other situations where I had the same configuration, I did not have such issue while migrating mailboxes to O365 in hybrid environment and cannot understand itRe: Local domain mailbox migration error
AnnTaeYoun I know that, but I'm talking about the "AD internal domain" which is by default added to all exchange users created. Each user has his primary SMTP address as user @ domain.com which is the public domain and an alias pointing to the AD domain domain.local. We made several migration and never happened that the internal AD domain was rejected during the migrationLocal domain mailbox migration error
I ran into an issue while migrating from on-premise to O365. On-premise AD domain is “domain.local” so users have their mailboxes smtp address as follows: primary smtp mailto:email address removed for privacy reasons ( public domain ) aliases smtp proxy: mailto:user@domain.local We setup the hybrid environment and started the mailbox migration but they’re failing with the error that domain.local is not an accepted domain in O365. this is the first time it occurred to us since we made a lot of migration so far What can it be ? obviously is not possible to add domain.local as accepted domain in o365
