Switch Practical in Cisco Packet Tracer (Step-by-Step Guide for Beginners)

If you’ve already learned hub networking, the next step is understanding how a network switch works. In this practical guide, you’ll build a simple LAN using a switch in Cisco Packet Tracer and observe how intelligent data forwarding improves network performance.

📌 What is a Switch?

A switch is a networking device that operates at the Data Link Layer (Layer 2) of the OSI model.

👉 Key features:

• Uses MAC address table for forwarding
• Sends data only to the intended device
• Reduces network traffic
• Supports full-duplex communication
• Creates separate collision domains per port

🧪 Lab Objective

• Create a LAN using a switch
• Connect multiple PCs
• Configure IP addresses
• Test connectivity using ping
• Observe packet flow in simulation mode
• Compare behavior with a hub

🛠️ Requirements

• Cisco Packet Tracer installed
• Basic knowledge of IP addressing

🔌 Step 1: Create Network Topology

Open Packet Tracer

Drag and drop:

1 Switch (e.g., 2960)

6 PCs (PC0 to PC5)

Connect all PCs to the switch using:

Copper Straight-Through Cable

👉 This forms a star topology, similar to hub setup but smarter.

🌐 Step 2: Configure IP Addresses

Assign IP addresses manually:

📍 Path:

PC → Desktop → IP Configuration

👉 No default gateway required for same network communication.

📡 Step 3: Test Connectivity

Go to PC0 → Command Prompt:

ping 192.168.1.6

👉 You should receive successful replies.

🎬 Step 4: Enable Simulation Mode

• Click Simulation Mode
• Click Edit Filters
• Click Show All / Enable All

👉 This ensures ARP and ICMP packets are visible.

📦 Step 5: Observe Packet Flow

Run the ping again and click:

Auto Capture / Play (▶▶)

OR

Capture/Forward (▶)

🔍 What Happens Behind the Scenes?

1️⃣ ARP Request (Broadcast)

PC0 asks: Who has 192.168.1.6?

Switch forwards to all devices (initially)

2️⃣ MAC Address Learning

Switch learns:

PC0 MAC → Port X

PC5 MAC → Port Y

👉 Stored in MAC Address Table

3️⃣ ICMP Packet (Smart Forwarding)

After learning:

Switch sends packet:

PC0 → Switch → PC5 ONLY

👉 Unlike a hub, it does NOT broadcast to all devices.

⚠️ Important Observations

• First communication involves broadcast (ARP)
• After learning, communication becomes direct and efficient
• Network traffic is significantly reduced

🔄 Switch vs Hub (Practical Difference)

🧠 Real-World Importance

Switches are widely used in:

• Office networks
• Data centers
• Enterprise environments

👉 They are the backbone of modern LANs.

🚀 Mini Practice Task

• Run ping PC0 → PC5
• Clear simulation
• Run ping again

👉 Observe:

• First ping = broadcast + learning
• Second ping = direct communication

💡 Conclusion

This practical demonstrates how a switch intelligently forwards data using MAC addresses, reducing unnecessary traffic and improving network efficiency. Compared to hubs, switches offer better performance, scalability, and security, making them essential in real-world networking.

Hub Practical in Cisco Packet Tracer (Step-by-Step Guide for Beginners)

If you're starting your networking journey, understanding how a hub works is fundamental. In this practical guide, we’ll build a simple network using a hub in Cisco Packet Tracer and observe how communication happens between devices.

📌 What is a Hub?

A hub is a basic networking device that operates at the Physical Layer (Layer 1) of the OSI model.

👉 Key characteristics:

• Broadcasts data to all connected devices
• No intelligence (doesn’t store MAC addresses)
• Works in half-duplex mode
• Creates a single collision domain

🧪 Lab Objective

• Create a network using a hub
• Connect multiple PCs
• Configure IP addresses
• Send data from one PC to another
• Observe packet flow using simulation

🛠️ Requirements

• Cisco Packet Tracer installed
• Basic understanding of IP addressing

🔌 Step 1: Create Network Topology

1. Open Packet Tracer

2. Drag and drop:

   # Hub

   # PCs (PC0 to PC5)

3. Connect all PCs to the hub using:

   # Copper Straight-Through Cable

👉 Your topology should look like a star network with a hub at the center.

🌐 Step 2: Configure IP Addresses

Assign IP addresses manually to each PC:

📍 Path:

Click PC → Desktop → IP Configuration

👉 No default gateway needed (no router involved)

📡 Step 3: Test Connectivity

Go to PC0 → Command Prompt and run:

ping 192.168.1.6

👉 If configured correctly, you’ll receive replies.

🎬 Step 4: Enable Simulation Mode

Click Simulation Mode (bottom right)

Click Edit Filters

Click Show All / Enable All

👉 This step is critical—without enabling protocols like ARP and ICMP, packets won’t be visible.

📦 Step 5: Observe Packet Flow

Now run the ping again and click:

#. Auto Capture / Play (▶▶)

OR

#. Capture/Forward (▶)

🔍 What Happens Behind the Scenes?

1️⃣ ARP Request (Broadcast)

PC0 asks: Who has 192.168.1.6?

Hub sends this request to all PCs

2️⃣ ARP Reply

PC5 responds with its MAC address

3️⃣ ICMP (Ping)

Actual communication occurs

👉 You’ll see packets traveling across all connections due to hub behavior.

⚠️ Important Observations

• All devices receive the data (not just the destination)
• Network traffic increases unnecessarily
• Collisions may occur

❌ Limitations of Hub

• No security
• No traffic filtering
• Poor performance
• Outdated technology

🔄 Hub vs Switch (Quick Comparison)

🚀 Conclusion

This practical demonstrates how a hub blindly forwards data to all connected devices. While hubs are no longer used in modern networks, understanding them builds a strong foundation for learning switches and advanced networking concepts.

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical,User account disablement is a common L1-level ticket in enterprise environments. It may occur due to HR actions, security policy enforcement, inactivity, or administrative changes. L1 engineers must verify the reason carefully before enabling the account to avoid policy violations. This guide explains the standard enterprise workflow for handling disabled user accounts using Active Directory.

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Unlock user
2. Reset password
3. Enable / Disable account
4. Create new user
5. Add user to group
6. Remove user from group
7. Check login issues
8. Move user to correct OU
9. Basic permission via groups

Today we will see step by step Account & License Management  

👤 SCENARIO 1 — Enable / Disable account

 
🚫 SCENARIO — User Account Disabled


User account disablement is a common L1-level ticket in enterprise environments. It may occur due to HR actions, security policy enforcement, inactivity, or administrative changes. L1 engineers must verify the reason carefully before enabling the account to avoid policy violations.

This guide explains the standard enterprise workflow for handling disabled user accounts using Active Directory.


🔎 Symptoms Observed

• Users typically report:
• Cannot login to system
• Error message: “Your account has been disabled. Please contact your system administrator.”
• Outlook not connecting
• VPN authentication failing
• Teams login failure

1️⃣ Step 1 — Verify the Scenario (Important)

Before enabling the account, confirm:

Is this a rejoining employee?

Has HR approved account activation?

Is there an open service request ticket?

Was the account disabled due to security reasons?

Is this part of offboarding process?

⚠ Never enable an account without proper authorization.

2️⃣ Step 2 — L1 Action (Enable / Disable Account Procedure)

🖥 Using Active Directory Users and Computers (ADUC)

Method 1 — Via Properties

• Open ADUC
• Search for the user
• Right-click → Properties
• Go to Account tab
• Uncheck: Account is disabled
• Click Apply → OK

Method 2 — Quick Right-Click Option

• Open ADUC
• Locate the user
• Right-click on user

Select:

• ✔ Enable Account (if disabled)
• ✔ Disable Account (if requested by HR/Security)
• This is the fastest method used in L1 operations.

3️⃣ After Enabling — Inform the User

• Advise the user to:
• Lock PC (Windows + L)
• Log in again
• Connect VPN if working remotely
• Restart system if required
• If password expired, perform password reset as per policy.

4️⃣ When L1 Should Disable an Account

• L1 may disable accounts in cases such as:
• HR termination ticket
• Long leave request
• Security instruction
• Contract completion
• Lost device security precaution
• Always document ticket number and approval source.

🚨 Escalate If

• Immediately escalate to L2 / Security / HR if:
• Account disabled due to HR termination
• Security suspension case
• Insider threat investigation
• Legal hold case
• Unknown disablement with no ticket reference
• Account automatically re-disables (possible GPO or sync issue)

🧠 Real Helpdesk Insight

• In hybrid environments (On-Prem AD + Azure AD sync):
• If account is enabled in AD but still blocked in Microsoft 365
• Check Azure AD sync status
• Confirm sign-in status in Microsoft 365 Admin Center
• Sometimes cloud sign-in may be blocked separately.

✅ L1 Checklist (SOP Format)

• ✔ Identity verified
• ✔ Ticket approved
• ✔ Checked reason for disablement
• ✔ Account enabled via ADUC
• ✔ User informed
• ✔ Login tested
• ✔ Escalated if policy-related

🎯 Interview-Ready Statement

If interviewer asks how you handle disabled account cases:


“First, I verify the reason for disablement through ticket and HR approval. I never enable accounts without authorization. After validation, I enable the account via ADUC either through Properties → Account tab or right-click enable option. Then I guide the user to log in and monitor for replication issues. If the disablement is related to HR or security, I escalate immediately.”

Disclaimer

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical, User onboarding is a critical responsibility for L1 Desktop Support teams in enterprise environments. When a new employee joins, IT must ensure proper account creation, access provisioning, and mailbox setup without security gaps or permission errors. In hybrid environments (On-Prem AD + Microsoft 365), the process involves Active Directory configuration followed by synchronization to Azure AD. This guide explains the standard real-world workflow followed by service desk engineers during new user creation.

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Unlock user
2. Reset password
3. Enable / Disable account
4. Create new user
5. Add user to group
6. Remove user from group
7. Check login issues
8. Move user to correct OU
9. Basic permission via groups

Today we will see step by step Account & License Management  

👤 SCENARIO 1 — Create new user (new user join)

✅ Step 1 — Create User in Active Directory


User accounts are created in:

Active Directory Users and Computers (ADUC)

You can open it via:

• dsa.msc

📍 Navigate to Proper OU


Inside ADUC:

 

• Expand Domain Name (Example: company.local)
• Navigate to correct OU (Organizational Unit) – e.g., Accounts / Users
• Right-click the OU
• Select New → User
• Fill Required Details:
• First Name
• Last Name
• Full Name
• Username (SamAccountName)
• User Logon Name (UPN)
• Click Next

Set Password & Account Options:

✔ User must change password at next login
✔ Password never expires (Company policy based)
✔ Account enabled


Click Next → Finish

User account is successfully created.




🎯 Best Practice

• Always create users inside the correct OU to ensure:
• Proper Group Policy application
• Security compliance
• Automatic script execution (if configured)

✅ Step 2 — Add User to Security Groups

After account creation, assign access based on job role.

Most Used Method:

• Right-click User
• Select Properties
• Go to Member Of tab

You may see default group:

Name            | Location
-----------------------------------
Domain Users    | test.com/Users
To Add User to Required Groups:

Click Add

• Enter group name (e.g., VPN_Users, Email_Users, Finance_Share)
• Click Check Names
• Click OK
• Click Apply
• Typical Groups Assigned:
• Email Access Group
• VPN Access Group
• File Server Access Group
• Printer Access Group
• Department Security Group

💬 Professional Interview Answer Line

“I will open ADUC using dsa.msc, navigate to the appropriate OU, create a new user via New → User, configure password policies, enable the account, and assign necessary security groups through the Member Of tab to provide email, VPN, file, and printer access based on the user’s role.”

✅ Step 3 — Inform Microsoft 365 Admin (Hybrid Environment)

• If organization uses Hybrid AD setup:
• User account syncs via:
• Azure AD Connect

Process:

• Wait for Azure Sync cycle
• Verify user appears in Microsoft 365 Admin Center
• License will be assigned by M365 Admin team
• Once license is assigned:
• Mailbox gets provisioned
• Teams access enabled
• OneDrive created

🔍 Verification Steps After Sync

• Check user appears in Microsoft 365 portal
• Confirm license assigned
• Verify mailbox created in Exchange Online
• Confirm Teams login works

🚨 Step 4 — Escalation Criteria

• Escalate to L2 / Cloud Admin if:
• User not syncing to Azure AD
• Sync errors in Azure AD Connect
• No mailbox created after license assignment
• Duplicate UPN conflict
• Azure AD provisioning issue

Before escalation, document:

• OU location
• Groups assigned
• Time of account creation
• Sync cycle time
• Error screenshot (if any)

📝 Real Helpdesk Documentation Format

Request: New User Creation – Finance Department
Action Taken:
Created user in AD → Assigned groups → Confirmed sync → Informed M365 admin

Pending: License assignment
Status: Awaiting mailbox provisioning

🔐 L1 Best Practices

• ✔ Always verify HR approval before account creation
• ✔ Follow naming convention standard
• ✔ Assign minimum required permissions (Least Privilege Principle)
• ✔ Confirm department-specific groups
• ✔ Document everything in ticket

✅ Quick Checklist Summary

• ✔ Create user in correct OU
• ✔ Set password policy
• ✔ Enable account
• ✔ Add required groups
• ✔ Wait for Azure sync
• ✔ Inform M365 Admin
• ✔ Verify mailbox creation

Disclaimer

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical, In enterprise environments, users are organized in Organizational Units (OUs) within Active Directory to apply department-based policies, security controls, and access permissions. When an employee changes department, role, or location, moving the user to the correct OU becomes an essential L1 support task.

Improper OU placement can result in login issues, incorrect Group Policy Objects (GPOs), missing permissions, or security misconfiguration. This guide explains the standard L1 workflow for safely moving users between OUs.

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Unlock user
2. Reset password
3. Enable / Disable account
4. Create new user
5. Add user to group
6. Remove user from group
7. Check login issues
8. Move user to correct OU
9. Basic permission via groups

Today we will see step by step Account & License Management  

📂 SCENARIO — Move User to Correct Organizational Unit (OU)

 Here is your complete structured blog article content for the title:



🔎 When Is This Required?

• This action is typically performed when:
• Employee department changed (e.g., Sales → IT)
• Role or designation updated
• Location transfer (Branch change)
• GPO policy needs to be updated
• Access level needs to align with new department
• Incorrect OU placement during user creation

1️⃣ Step 1 — Verify Authorization

• Before moving the user:
• Confirm HR approval or official department change email
• Ensure service request/ticket is raised
• Verify new department details
• Confirm correct destination OU name
• ⚠ Never move users without documented approval. OU structure affects security policies.

2️⃣ Step 2 — L1 Action (Move User in ADUC)

🖥 Using Active Directory Users and Computers (ADUC)
 

Method 1 — Drag & Drop (Most Common)

 

• Open ADUC
• Locate the current OU (e.g., Sales)
• Find the user account
• Drag and drop the user into the new OU
• Example:
• Sales → IT Department OU
• Confirm the move

Method 2 — Right-Click Move Option

• Open ADUC
• Right-click the user
• Select Move
• Choose the correct destination OU
• Click OK
• This method is safer when OU hierarchy is complex.

< br />

3️⃣ Post-Move Validation

• After moving the user:
• Run gpupdate /force on user machine (if required)
• Ask user to log off and log back in
• Verify:
• Folder access
• Application access
• Network drive mapping
• Printer access
• Confirm Outlook and VPN working properly
• GPO policies may take time depending on replication and site configuration.

4️⃣ Common Issues After OU Move

• Sometimes after moving a user:
• Login takes longer (GPO processing)
• Access to previous department resources removed
• New drives not mapping
• Restrictions applied due to tighter policies
• MFA / conditional access behavior changes (hybrid setup)
• Always inform user about possible policy refresh delay.

🚨 Escalate If

• Escalate to L2 / AD Team if:
• User cannot login after OU move
• GPO not applying properly
• Access conflicts occur
• Replication issues between Domain Controllers
• Hybrid sync issue (Azure AD Connect)
• OU protected from accidental deletion and move fails
• 🧠 Real Helpdesk Insight

OUs are often linked to:

• Group Policy Objects (GPOs)
• Login scripts
• Security baselines
• Software deployment policies
• BitLocker / Endpoint policies
• Moving a user changes all applied policies. Always double-check the destination OU.

✅ L1 Checklist (SOP Style)

• ✔ HR/Manager approval verified
• ✔ Ticket logged
• ✔ Correct OU identified
• ✔ User moved via ADUC
• ✔ GPO refresh completed
• ✔ User login tested
• ✔ Access validated
• ✔ Escalated if required

🎯 Interview-Ready Answer

If interviewer asks how you move a user to a different department:

“First, I verify HR approval and the correct target OU. Then I use ADUC to move the user either via drag-and-drop or the Move option. After the move, I ensure Group Policy refresh and validate that the user has appropriate access based on the new department. If GPO or replication issues occur, I escalate accordingly.”

Disclaimer

LAN Cable Lights Explained: What Do Those Blinking LEDs Mean?

If you’ve ever plugged in a LAN cable and noticed two tiny blinking lights near the port, you’re not alone in wondering what they actually mean. These lights aren’t random—they’re quick indicators of your network connection status and performance.

1. Green Light – Connection & Activity

The green LED tells you whether your device is connected and actively communicating.

* **Solid Green:** Your device is properly connected to the network.

* **Blinking Green:** Data is being transferred (internet activity).

* **Off:** No connection detected—check your cable or port.

2. Orange (or Amber) Light – Speed & Performance

The orange light usually indicates the speed or quality of your connection.

* **Solid Orange:** High-speed connection (often 1 Gbps).

* **Blinking Orange:** Ongoing network activity.

* **Off:** Lower speed connection (like 10/100 Mbps) or limited capability.

Why This Matters

These small LEDs are actually powerful diagnostic tools. If your internet feels slow or isn’t working, a quick glance at these lights can help you identify whether the issue is with the connection, cable, or network speed.

Final Thoughts

Next time you see those blinking lights, you’ll know they’re not just flickering randomly—they’re giving you real-time feedback about your network health. Understanding them can save you time when troubleshooting and help you keep your connection running smoothly.

Azure Pricing & Cost Management

Azure is one of the most popular cloud platforms, and many learners are eager to get started. However, beginners often feel overwhelmed due to the wide range of services and concepts. If you have no prior experience in cloud computing or Azure, the best place to start is with Azure Fundamentals (AZ-900). In this blog series, we will cover both theoretical concepts and practical hands-on exercises to help you build a strong foundation in Microsoft Azure.

We will also provide a real-world, enterprise-level roadmap to guide your learning journey step by step.


For Phase 1 (Cloud Fundamentals) the topics I listed are sufficient to understand Azure basics, but if your goal is to prepare properly for Microsoft Certified: Azure Fundamentals (AZ-900) and to build a solid base for later phases, you should expand Phase 1 slightly. 

Think of Phase 1 as “cloud literacy + Azure platform orientation.
Below is a complete but still beginner-level Phase 1 syllabus.


Phase 1 — Azure Fundamentals (Expanded) - CLICK HERE 

Phase 2 — Azure global infrastructure regions availability zones  (Expanded) - CLICK HERE   

Phase 3 — Azure core services compute storage networking overview  (Expanded) - CLICK HERE    

Phase 4 — azure-identity-access-management-entra-id-rbac-mfa-sso
(Expanded) - CLICK HERE 

5. Azure Pricing & Cost Management

 
Very important in cloud environments.

Topics:

• Pay-as-you-go model
• Pricing calculator
• Total cost of ownership
• Cost management dashboard
• Resource tagging

Describe factors that can affect costs in Azure

Azure cost depends on what you use, how much you use, and how you configure it.

OR

Azure costs are influenced by factors such as resources type, consumption, maintenance, geography, subscription type, and azure marketplace usage.




Core Idea 

Azure = Pay as you use
More usage -> More cost
Less usage -> Less cost

🔥 6 Main Factors That Affect Cost

Just remember this -> R, C, M, G, S, M

1. Resource type
2. Consumption
3. Maintenance
4. Geography
5. Subscription type
6. Azure marketplace




🧠 Now Understand Each in Simple Terms

🔹 1. Resource Type

Different services = different cost

Example:
VM (expensive)
Storage (cheaper)

Also depends on:
Size
Configuration
Region

img src - learn.microsoft.com

🔹 2. Consumption (VERY IMPORTANT 🔥)

You pay based on usage

Example:

More VM hours -> more cost
Less usage -> less cost


Cost saving option


Pay-as-you-go -> flexible
Reserved -> cheaper (long-term)
Savings plan -> flexible discount
Spot VM -> cheapest (but can stop anytime)

3. Maintenance

 

Unused resources still cost money

Example:

Deleted VM but storage still running -> still paying
Clean unused resources = save money

4. Geography

Location affects cost

Example

India vs US -> different pricing 

also:

Data transfer cost changes by region

5. Subscription Type 

There are different subscription types:

Free credit
Discounts
Limits



Example:

Free trial -> free credit 
Discounts
Limits


Example:

Free trial -> free credits

6. Azure Marketplace

Third-party services cost extra

Example:

Prebuilt software
Paid tools


You pay:

Azure cost + vendor cost





Bonus transfer matters:

Incoming data -> mostly free
Outgoing data -> Cost

What is Cost management ?

Cost management provides the ability to quickly check azure resources costs, create alerts based on resource spend, and create budgets that can be used to automate management of resources.

Credit alerts

Credit alerts notify you when your azure credit monetary commitments are consumed. Monetary commitments are for organization with enterprise agreements (EAs). Credit alerts are generated automatically at 90% and at 100% of your azure credit balance. Whenever an alerts is generated, its reflected in cost alerts, and in the email sent to the account owners.

Thank you for sharing - sharing is caring :-)