Видео

Thanks for the suggestion, stay tuned!

Our pleasure!

I'm glad you found it helpful!

Definitely....your suggestions are very valuable and the videos will come shortly...Keep watching

Thanks for the kind words - I'm glad you're finding the videos helpful!

Glad it helped!

Glad you found it useful

Always welcome

Please try to answer...

The answer is on its way in the upcoming video, keep watching

It's my pleasure

Thanks for the comments, keep watching

The main difference between DAS (Direct Attached Storage) and NAS (Network Attached Storage) lies in how they are accessed and managed, despite both being accessible over the network. 1. DAS (Direct Attached Storage): Direct Connection: DAS is physically attached to a single computer or server through interfaces like SATA, SAS, or USB. It's not designed to be a networked storage solution by default. Network Access via Sharing: Network users can access those files if a server with DAS is connected to a network and shares folders or drives. However, the key here is that the storage still depends on the host system (the server) for access control, file sharing, and performance. Usage: DAS is typically used in scenarios where storage needs are local to a single server or system. It requires manual configuration to share files across the network. 2. NAS (Network Attached Storage): Dedicated Network Storage: NAS is specifically designed to be a standalone storage device connected directly to a network. It has its own operating system and file-sharing protocols (like SMB, NFS, etc.), meaning it doesn't depend on a specific server or computer to share files. Access Control and Features: NAS devices offer built-in features for network access, including user authentication, RAID management, file permissions, and sometimes cloud integration. These features are independent of any server and are optimized for network-based access. Usage: NAS is used in environments where multiple users or devices need access to shared storage over a network, with efficient file sharing and centralized management. Key Differences: Access Dependency: DAS relies on the host server to provide network access, while NAS operates independently and directly connects to the network. Management: NAS comes with its own management tools, access controls, and features optimized for network environments, whereas DAS requires more manual configuration and lacks the network-specific features of NAS. Performance and Scalability: NAS is better suited for multiple users accessing storage over a network. DAS is more limited to the performance and scalability of the host system. When to use NAS vs DAS: DAS is good when storage is required for a single system or if network file sharing is only a secondary concern. NAS is ideal for scenarios where multiple users need access to storage across a network with better management and access controls, making it a more robust solution for shared environments. In summary, while both can allow users to access data over the network, NAS is purpose-built for that function and offers more flexibility, management, and reliability for network storage, while DAS is primarily local storage with optional network access via a server.

​@@dctechnetthank you for all this info! What would you buy if you cared most about not losing data either with redundancy or other means (priority 1, 2, and 3). Distant second would transfer speed and accessibility but desired. Lastly, it would be cool if it had on/off switches to not use up the life of the drives unless you wanted them running. What would you use for both hardware and software? Scenario 1: 5x 5TB drives and Direct Connection across both a stationary Laptop and Desktop that can be moved for portability if needed but almost never moves. Scenario 2: Same but will be moved frequently to many rooms in the house or another house. Many thanks!!!

Sure

We have a recent video on Sites and Services ruclips.net/video/HO1R1l8C-z0/видео.html

List of fictional Microsoft companies microsoft.fandom.com/wiki/List_of_fictional_Microsoft_companies Microsoft uses a variety of fictional company names in the documentation and training material for its products. Microsoft documentation and learning materials often contain fictional scenarios and descriptions of how their products can be deployed and used in these scenarios. Many of these companies are used in such examples. Some of the fictional companies have associated websites, almost all of which redirect to microsoft.com.

You're welcome!

Sure I will...Many thanks for the suggestion

Yes...

Thanks for the feedback...Yes, I agree...I made a mistake...I would have assigned it to MADRID Site.

Thanks for the comment - We need to create 2 groups one for READ and another for MODIFY

Send a test mail to dctechnet@outlook.com

I do not have a LinkedIn account

@@dctechnet its sad to hear that 😔, thank u for sharing ur knowledge with us, u are such a kind person may God reward u .😇

192.168.100.0/24 and 172.16.0.0/24 are two different networks still it works as we have configured a Windows Server as a router in the earlier session ruclips.net/video/Iqe6NncnwbE/видео.html

Thanks for liking

Thanks

Thank you! Cheers!

Thanks and welcome...

So nice of you

Glad you enjoyed it

Most welcome

Most welcome

Highly appreciate you comments....

Please elaborate your query

So nice of you

Thanks for the suggestion - We are already working on a deep dive series on DNS, please give us some time....

Thanks and welcome

So nice of you

Consistency Across the Domain: Active Directory is designed to ensure that all DCs have consistent and up-to-date information. Even if the user never logs on in Site B, other services or applications might rely on the updated credentials being available on all DCs. Authentication Redundancy: If the user were to travel to Site B or if there is a network issue preventing them from authenticating with a DC in Site A, they could still log on using a DC in Site B. Replicating the password change ensures that the user's new credentials are recognized, avoiding potential login issues. Global Access and Security: Some applications and services may authenticate against a DC in Site B, even if the user is primarily based in Site A. For example, if a service in Sydney needs to validate the user’s credentials, the updated password must be available on the DCs in that site. Disaster Recovery: In case of a disaster that affects Site A, the DCs in Site B would still have the updated information, ensuring that the user's credentials are valid and available. In summary, inter-site replication occurs to maintain data consistency, support redundancy, and disaster recovery, and ensure seamless access to services across the entire Active Directory environment. *** Hope this is helpful ....

@@dctechnet Thank you Sir, but if we will replicate data between all Sites so why using the Global Catalogue ? Also for remote access its the Admin who decide which domain and site the client have access to, as he's the one who provide him with an ip address that belongs to that specific site, in Addition that the number of people that should have access to all sites are few, and the horrible thing is if a hacker get managed to hack one site he will gain the whole information as the DCs of that site had replications from the other sites's DCs, why we prefer consistency over security ?

Q1-but if we will replicate data between all Sites so why use the Global Catalogue? Please watch this video in complete, especially "Functions of GC" - ruclips.net/video/cIs5Zc-7Ps4/видео.html Also for remote access its the Admin who decides which domain and site the client have access to, as he's the one who provides him with an IP address that belongs to that specific site, in Addition that the number of people that should have access to all sites are few, and the horrible thing is if a hacker get managed to hack one site he will gain the whole information as the DCs of that site had replications from the other sites DCs, why we prefer consistency over security? - That’s the reason organizations implement RBAC. The access is not “site-based” it’s “Role-based”, That’s the reason Microsoft came up with the concept of “Built-in Groups in Active Directory” why do we prefer consistency over security? - Security has the highest precedence in the world of AD. I would also recommend watching ruclips.net/video/5N242XcKAsM/видео.html Kerberos Authentication Explained | A deep dive & ruclips.net/video/kp5d8Yv3-0c/видео.html How Kerberos Works in Windows Active Directory - (These videos are not my video)

@@dctechnet thanks Sir

Thank you so much for your kind words! We are thrilled to hear that the video helped clarify the concepts for you. It's comments like yours that inspire us to keep creating content. We'll keep doing our best to deliver videos that are both informative and easy to understand. Stay tuned for more, and thanks for your continued support!

I am glad you liked it...

Always welcome

Welcome

??

Always welcome

AD Sites and services video will be uploaded soon...

Will do soon...Thanks for the suggestion

So nice of you

Glad you liked it

Glad you liked it

Glad you liked it

@@dctechnet please explain clear cut different kerbros and domain controller

Also explain user authentication processed by kerbros protocol Or domain controller? Kerbros is part of domain controller?