Er. Himanshu Shukla

Solaris 10 patching details.. https://lnkd.in/giRaEvCw Lean patching no i.e..other way of patching is not given..create mount point which is temp..make it dynamic for 3 hrs time.. The old sol..8 upgrade is given below..as well dynamic mount for latency patch..because legacy patch should be done via 3rd party ..use this for specficed purpose..no change in log...

1

Upgrading from SCCM Current Branch 2303 to 2403 requires careful planning to minimize downtime and ensure a smooth transition. # Preliminary Checks 1. *Review the Release Notes* - Understand the new features and changes in #SCCM Current #Branch 2403. Note any deprecated features, new hardware/software requirements, and other critical changes. 2. *Check System Requirements* Ensure your current hardware operating system, #database, and network configuration meet or exceed the requirements for SCCM 2403. 3. *Backup Your SCCM Environment* Perform a full #backup of the SCCM site database, site server, and other critical data.This ensures you can recover if anything goes wrong during the upgrade. 4. *Check the Version of #SQL Server* Verify that your SQL Server version is compatible with SCCM 2403. Upgrade if necessary. 5. *Ensure User Permissions* - Confirm that you have administrative permissions for the SCCM site server and SQL Server. 6. *Review Customizations* - Document any custom scripts, reports, or other configurations. Understand how the #upgrade might affect these. 7. *Evaluate Client Versions* - Ensure that your SCCM clients are at a version that supports upgrade to 2403. # Pre-Upgrade #Tasks 8. *Check for Prerequisite Updates* - Install any prerequisite updates required for SCCM 2403. 9. *Review Windows Updates* - Ensure that your #Windows Server and client machines are fully updated. 10. *Ensure Enough Disk Space* - Confirm there is sufficient disk space for the upgrade. 11. *Disable Third-Party Software* - Temporarily disable antivirus or other third-party #software that might interfere with the upgrade. # Perform the Upgrade 12. *Download the SCCM Update* - Access the "Updates and Servicing" node in SCCM and check for updates. Download the update for 2403. 13. *Start the Update* - Once the update is downloaded, start the installation #process from the SCCM console. Monitor the process for any errors. 14. *Verify the Upgrade* - After the update is completed, check the #SCCM console to ensure everything is working as expected. 15. *Check Client Updates* - Deploy the client #update to ensure all clients are upgraded to the latest version. # Post-Upgrade Tasks 16. *Validate Functionality* Test #critical functionalities, including software distribution, OS deployment, software updates, and reporting. 17. *Check for Errors or Alerts* Review the SCCM logs and console for any errors or warnings. 18. *Re-enable Third-Party Software* - Once the upgrade is confirmed as #successful, re-enable any #software you had disabled earlier. 19. *Backup Again* - After the upgrade is complete and verified, take another #backup to capture the new configuration. 20. *Document the Upgrade* - Record the upgrade process, including any issues encountered and their #resolution. If you encounter issues, consider reaching out to #Microsoft #Support for further assistance.

42

3 Comments

New Post | Learn how to find #BIOS details using #CMPivot query such as BIOS version, manufacturer, on all your #Windows devices managed by #SCCM https://lnkd.in/g48un4Fq #windows11 #windows10

54

As VMware vSphere environments began to grow, a vSphere Standard Switch (VSS) is not well-equipped to satisfy the networking needs of large environments. If you create a vDS in vCenter, identical hidden vSS are created on all ESXi hosts added to VDS configuration. When you create a port group (PG) for VLAN on a vDS, the same port group will be created on all Virtual Switches of ESXi hypervisor attached to that VDS. Some advantages that are available on a distributed virtual switch are:   (1) Central Management of all ESXi host’s networking (2) The ability to enable Network IO Control (NIOC)  (3) NetFlow support, is only supported with vDS  (4) Port Mirroring to clone traffic from one port to another  (5) LACP between vSphere hosts and the access layer physical switch Requires Enterprise Plus licensing from VMware. Individual host-level virtual switches are connected to one large VDS spanning multiple hosts at the data-center level. The data plane remains local to each VDS but the management plane is centralized. (*) The vDS or dvuplink port group, is first one when you create a vSphere Distributed Switch to which it is associated. (*) The vSphere Distributed Switch port groups, provide network connectivity to VMs and also provide the channel for VMkernel traffic.  VMware Education | https://lnkd.in/ez97H_St VMware Consulting | https://www.ITSA.Cloud

8

Definitely prefer offline patching #leadership #management #technology #informationsecurity #ciso #riskmanagement #security #cybersecurity #privacy

64

4 Comments

Okay, the VMs will definitely power off and if vSphere High Availability (HA) was correctly configured in the cluster nothing should happen to the VMs. The VMs will try to restart on another host, but there are things that will stop a Virtual Machine from being restarted on another Hypervisor like “restart policy”. If HA is enabled but the Virtual Machine restart policy is disabled then the VM will not be restarted on another host ignoring the HA master election process. Also, an incorrect Admission Control settings & resource availability on the host will stop the VMs to restart on another ESXi. Hey guys, the key thing to remember is that HA will not trigger a vMotion. On the other hand, check to see if the cause is affected hardware or software components. Try to Identify the problem: * Check if the vSphere ESXi is powered on by checking logs * Reconnect a disconnected host from the vCenter server * Check connectivity via Windows CMD FQDN and IP address or another ESXi * Verify port 902 must not be blocked between the vSphere Client and the hosts  * Try restarting ESXi management agents. Troubleshoot the VPXA agent * Check underlying storage issues, protocols like iSCSI, NFS, or SAN VMware Education | https://lnkd.in/ez97H_St VMware Consulting | https://www.ITSA.Cloud

5

Unlock the power of access control with IAM essentials: Users, Groups, Roles, and Policies. Learn how they shape permissions and security protocols! 💡💻 Visit us at www.jamanispeshpro.com OR Contact us at +91 6283047709 / business@jamanispeshpro.com #IAM #AccessControl #Security #Users #Groups #Roles #Policies #Amazonwebservices #amazoncloud

4

This will ease your azure config to active directory and help with load balancing for creating you AG on VMs. #Azure #VM #Cloud

1

Okay, the VMs will definitely power off and if vSphere High Availability (HA) was correctly configured in the cluster nothing should happen to the VMs. The VMs will try to restart on another host, but there are things that will stop a Virtual Machine from being restarted on another Hypervisor like “restart policy”. If HA is enabled but the Virtual Machine restart policy is disabled then the VM will not be restarted on another host ignoring the HA master election process. Also, an incorrect Admission Control settings & resource availability on the host will stop the VMs to restart on another ESXi. Hey guys, the key thing to remember is that HA will not trigger a vMotion. -Raul VMware Education | https://lnkd.in/ez97H_St VMware Consulting | https://www.ITSA.Cloud

5

#Learning #Uninstalling #impacted #patches, SCCM involves several steps. Here's a general process to guide you through: #Step 1: Identify the Impacted Patches 1. Determine the KB Numbers: Identify the Knowledge Base (KB) numbers of the patches you need to uninstall. 2. Create a List: Make a list of the affected servers that have these patches installed. #Step 2: Create a Package in SCCM 1. Open SCCM Console: Launch the SCCM console and navigate to the Software Library. 2. Create a Package: - Go to `Software Library > Application Management > Packages`. - Right-click on Packages and select `Create Package`. - Fill in the necessary details like Name, Description, Manufacturer, and Version. #Step 3: Add an Uninstall Program 1. Create a Program: - Right-click on the created package and select `Create Program`. - In the Program Type, choose `Standard Program`. - Provide a Name and Command line for the uninstall script. For example, for Windows patches, you can use: ``` wusa /uninstall /kb:<KB_Number> /quiet /norestart ``` - Replace `<KB_Number>` with the actual KB number of the patch you need to uninstall. - Configure other settings such as requirements, dependencies, etc. #Step 4: Distribute the Package 1. Distribute Content: - Right-click on the package and select `Distribute Content`. - Follow the wizard to distribute the package to the Distribution Points. #Step 5: Deploy the Uninstall Program 1. Deploy Program: - Go to `Software Library > Application Management > Packages`. - Right-click on the package and select `Deploy`. - Choose the collection of servers that need the patch uninstalled. - Specify the deployment settings such as purpose (e.g., `Required`) and scheduling. #Step 6: Monitor the Deployment 1. Check Deployment Status: - Navigate to `Monitoring > Deployments`. - Select the deployment and view the status to ensure the uninstallation is progressing as expected. Example Script for Batch Uninstall If you have multiple patches to uninstall, you can create a batch file to uninstall all at once: ```batch @echo off wusa /uninstall /kb:123456 /quiet /norestart wusa /uninstall /kb:234567 /quiet /norestart wusa /uninstall /kb:345678 /quiet /norestart ``` Save this script as `uninstall_patches.bat` and use it as the command line in your SCCM program: ``` cmd.exe /c uninstall_patches.bat ``` #Troubleshooting - Logs: Check the logs on the client machines for errors. Logs such as `#execmgr.log` can provide information about the execution of the program. - Restart Considerations: Make sure to manage restarts appropriately, as uninstallation of updates might require a restart to complete. This process allows you to automate the uninstallation of problematic patches across multiple servers, ensuring consistency and efficiency. #If this assists you in resolving your inquiry, please indicate your appreciation by #liking and #sharing this post.

80

3 Comments

Hands-on lab experience configuring FortiGate in transparent mode for enhanced network security. Strengthen your skills in firewall configuration and management. https://lnkd.in/d9fpSDaK #FortiGate #TransparentMode #FirewallConfiguration #NetworkSecurity #ITInfrastructure #NetworkManagement #NetworkConfiguration #ITTraining #FirewallManagement #NetworkEngineering

1

Day 33: Splunk Enterprise Troubleshooting Use Cases - 33 The activity that happened was Upgrade.. Upgrade from 8.2.5 version to 9.2.0 version Deployment Server Issues Issue: When browsing the Forwarder Management, no Clients are displayed. Root Cause: Deployment Server’s outputs.conf was missing the new internal indexes (_dsclient, _dsphonehome, _dsappevent) Solution: Add new internal indexes (_dsclient, _dsphonehome, _dsappevent) to Deployment Server’s outputs.conf. #splunk #day33 #splunkadmin #splunkblogs #splunkengineer #splunklife #softmania #splunkmania #troubleshooting #splunktroubleshooting #linkedinseries

58

6 Comments

SaaS cybersecurity startup TAC Infosec reported a net profit of Rs 6.33 Cr in the financial year 2023-24 (FY24), a 23% jump from Rs 5.12 Cr in FY23. The startup, which listed on NSE Emerge last month, also saw its operating revenue zoom 17% to Rs 11.84 Cr during the year under review from Rs 10.09 Cr in FY23. Total expenditure for the fiscal stood at Rs 5.49 Cr, a 10% jump from the Rs 4.97 Cr it spent in the previous fiscal. The major contributor in its expense was employee benefit expenses, which jumped to Rs 3.68 Cr during the year under review from Rs 1.28 Cr in the previous fiscal.  🚀 Join the startup revolution! Follow StartupTrak for the latest and hottest startup news, inspiring stories, and game-changing innovations! 💯❤️🔥 . . #TACInfosec #Cybersecurity #SaaS #FinancialResults #FY24 #NetProfit #RevenueGrowth #NSEEmerge #BusinessUpdate #TechStartups #OperatingRevenue #ExpenseReport #EmployeeBenefits #TechInvestments #IndianStartups #CorporateEarnings #MarketNews #FinancialPerformance #InvestmentNews #TechNews #StartupNews #StartupTrak

1

Ahmedabad, join renowned #cybersecurity experts on the Panel Discussion "Winning Strategies for Cyber Consolidation & Communication". Learn how centralized strategies minimize complexity enabling you to articulate cybersecurity concerns effectively. Contact your #TrendMicro representative now for more details. #Ahmedabad #paneldiscussion #panel Dhaval Mankad Tarun Vijh Kunal Kimatkar

35

2 Comments

Resetting WMI (Windows Management Instrumentation) settings in SCCM (System Center Configuration Manager) typically involves stopping the WMI service, deleting the WMI repository, and then restarting the WMI service. Below is a basic script that you can use to perform these steps. Please note that running this script will disrupt any ongoing WMI activities on the machine, so use it with caution. ##powershell # Stop the WMI service Stop-Service-Name "winmgmt" -Force # Pause to allow the service to stop Start-Sleep-Seconds 5 # Delete the WMI repository Remove-Item -Path "$env:windir\system32\wbem\repository" -Recurse -Force #Start the WMI service Start-Service -Name "winmgmt" #Pause to allow the service to start Start-Sleep-Seconds 5 # Verify if the WMI service is running $wmiService = Get-Service -Name "winmgmt" if ($wmiService. Status -eq "Running") { Write-Host "WMI settings reset successfully." } else { Write-Host "Failed to reset WMI settings. Please check the WMI service status." }

60