Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Customizing the Taskbar in Windows 10 during OSD

Posted on December 10, 2015August 24, 2017 by Jörgen Nilsson

I wrote a blog post before on how to remove the Edge icon in the Taskbar on Windows 10, https://ccmexec.com/2015/12/removing-the-edge-icon-from-the-taskbar-during-osd/

This post will cover how to use the same scripts and deploy a customized Taskbar instead with the Internet Explorer shortcut instead of the Edge icon.

Custom_taskbar1

1. Download the Script from Technet Galleries https://gallery.technet.microsoft.com/Manage-the-taskbar-remove-c3024e40

2. Extract the content to a folder that can be used as package source. It should look like this.

Custom_taskbar7

3. In the ManageTaskbar folder Delete the “Quicklaunch” folder and the “TaskbandCU.reg” file
Custom_taskbar81

4. On a Windows 10 client modify the Taskbar as you want it to look like adding the IE icon in this case and removing the Edge icon.

5. Copy the folder “C:\Users\%username%\appdata\roaming\Microsoft\Internet Explorer\Quick Launch” folder to the “ManageTaskBar” folder in the structure show above.

6. Remove the space in the “Quick Launch” folder-name to “QuickLaunch”

7. Open the “QuickLaunch” folder and right-click on the the “User-Pinned” folder which is hidden and remove the Hidden attribute, including all subfolders.
Custom_taskbar518. Open Regedit and browse to the following key, “HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Taskband”

Custom_taskbar3

9. Right-click on the “Taskband” key and select to export it, save it under “ManageTaskbar” in the folder structure created earlier with the name “TaskBandCU.reg” so that the content of the “ManageTaskbar” folder once again looks like this.

Custom_taskbar81

10. Then you are ready to create a package as in the previous blog post and the result will be in this case a customized Taskbar with the IE icon instead of the Edge icon.

Enjoy!

  • Internet Explorer
  • Taskbar
  • Windows 10
  • 63 thoughts on “Customizing the Taskbar in Windows 10 during OSD”

    1. Pär says:
      December 15, 2015 at 10:06 am

      Thanks for the tip! I figured this one out from your last post.

      However, if you’re going to use in-place upgrade, you need to run this for existing accounts as well, so instead of adding the script to the default user’s RunOnce reg key, I’m using ActiveSetup so it runs once for all users.
      Another way could be to load all existing user accounts’ registry and add the RunOnce reg key.

      Reply
    2. Dave says:
      December 17, 2015 at 9:06 pm

      This is awesome stuff!!! Thanks a bunch. Really like how this also removes the store icon too with out the GPO. Keep it coming

      Reply
    3. Mike says:
      December 19, 2015 at 1:09 am

      I’ve tried this with no success. I’m guessing it’s because it’s an HKCU mod, which really doesn’t work during OSD. Is there another way to do this? I would love to have a way!

      Reply
      1. Jörgen Nilsson says:
        December 21, 2015 at 2:06 pm

        Hi,
        The HKCU mod is run using the runonce key in the registry once for each new user and runs from the local disc, so it works great. If you have existing, a.ka. you are using the inplace upgrade to Windows 10 you should put the command in as an activesetup as well.
        /Jörgen

        Reply
    4. Pingback: Windows 10 – Personnalisation de la barre de tâche pendant l’OSD – Les2t.fr Blog IT – TRARBACH Jean-Yves et THONON Stéphane
    5. Jay Kennedy says:
      January 15, 2016 at 6:31 am

      Thanks Jörgen , this works great and your instructions are easy to follow. However it only seems to work for me is the users have admin rights. Can this be modified to work for all users? Or have I done something wrong?

      Reply
      1. Jörgen Nilsson says:
        January 25, 2016 at 10:15 pm

        HI,
        That should not be that case as the user have permisisons to modify those folders per default..
        Could it be that you have some Powershell settings that block it?
        /Jörgen

        Reply
    6. Larry Dickerson says:
      January 26, 2016 at 11:54 pm

      hello

      This worked perfectly!!!

      Thank You

      Reply
    7. Deepu Koul says:
      January 28, 2016 at 5:04 pm

      I have applied the solution to MDT 2013 U2 but it seems not working with MDT deployment methods.

      Any comments would be good to help me further.

      Reply
      1. Jörgen Nilsson says:
        February 1, 2016 at 10:06 pm

        Hi,
        The biggest difference MDT -> SCCM is that MDT runs all commands as local admin but SCCM runs them as System. Haven’t tested it with MDT but will try to…. So the problem is most likely there somewhere.
        /Jörgen

        Reply
    8. Eddie Rio says:
      February 1, 2016 at 7:04 pm

      It did worked Amazingly!!
      Thanks

      Reply
    9. Pingback: Anpassa Windows 10 startMeny och Taskbar – Blogg om IT, Smarta hem och teknik.
    10. Peter says:
      February 23, 2016 at 5:08 pm

      The powershell script in runonce is not running, when new user is logging in. but when I run the script manually, it works. why??

      Reply
    11. Peter says:
      February 24, 2016 at 1:37 pm

      The powershell in the regkey runonce is not running. why not? if I run it manually it works fine.

      Reply
    12. Clay says:
      February 26, 2016 at 2:46 pm

      Hello. I was wondering – can you elaborate on this?

      “If you have existing, a.ka. you are using the inplace upgrade to Windows 10 you should put the command in as an activesetup as well.”

      I don’t have any experience with Active Setup, could you write down the steps I need to do in order to make this script work with an in-place upgrade to Windows 10? I’m trying to work it out on my own, but I’m stuck 🙂

      Reply
      1. Jörgen Nilsson says:
        March 2, 2016 at 6:09 am

        Hi,
        I will write a post on how to use it with an activesetup as soon as possible.
        /Jörgen

        Reply
    13. Blaine says:
      March 3, 2016 at 5:56 pm

      Hello.
      I can not get this to work using MDT 2013 with MDT deployment methods. Any Ideas?

      Reply
    14. Vegard Alsli says:
      March 14, 2016 at 7:20 pm

      Have they removed the Windows 7 way of doing things? This also worked in windows 8 if I remember correctly. https://blogs.technet.microsoft.com/askcore/2010/03/16/how-to-customize-the-windows-7-start-menu-and-taskbar-using-unattend-xml/

      Reply
      1. Jörgen Nilsson says:
        March 14, 2016 at 10:29 pm

        Hi,
        That is correct, the Windows 8 /8.1 scripts doesn’t work in Windows 10
        /Jörgen

        Reply
    15. Michael says:
      March 14, 2016 at 8:56 pm

      Hi Jorgen, I’m too need help to use this script to work on ‘existing user profile’, thanks a bunch…

      Reply
    16. Adam Johnson says:
      March 17, 2016 at 7:14 pm

      Jorgen, great article!

      Quick question – In regards to this registry key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Taskband –
      “FavoritesResolve”, I noticed the FavoritesResolve value contains the user profile name and computer name in the binary data. For instance the TechNet downloaded script of TaskBandCU.reg has username “administrator” and computer name “ek0002”. Have you seen this source username/computername in the binary data cause any issues when applying to other profiles? I haven’t seen anything come up with my testing but wanted to ask you.

      Reply
    17. Brad says:
      March 24, 2016 at 1:37 pm

      Thanks for this. Works like charm deploying Win10 with MDT. I also added to the reg file the key to disable cortana aswell it was a hkey/currentuser key.

      Reply
    18. Jonathan says:
      March 24, 2016 at 6:15 pm

      Jörgen, where exactly do you place this in the task sequence in SCCM? Thanks for your help

      Reply
    19. Peter says:
      March 29, 2016 at 5:08 pm

      In my Windows 10 there will be no Runonce command started. even a simple Notepad.exe will not been started. grrr

      Reply
    20. Jake says:
      March 29, 2016 at 11:08 pm

      Hi Jorgen,

      It appears as though when my users launch internet explorer from the shortcut filed I created it says that it’s from an unknown publisher and asks if they’re sure they want to run it. Is there any way to get around this, or did I somehow do something wrong?

      Reply
    21. Noah says:
      March 30, 2016 at 6:21 am

      I’m trying to implement this into my Win 10 OSD task sequence, and it was working, but isn’t anymore. I think it has to do with the fact that the registry key that’s being made, within the RunOnce, is under “Default” as opposed to “.Default”. I’m not able to find “Default” in my test builds after the OSD is finished, but I can find “.Default”, but there isn’t a “RunOnce” key in that location, just “Run”.

      Any suggestions?

      Reply
    22. Paul says:
      April 12, 2016 at 5:50 pm

      I have tried using this as part of OSD. It works the first time a user logs in, but on subsequent logins, the icons that are pinned to the taskbar have no icon (if I hover the mouse over them, they do show the name), and nothing happens when I click on any of the icons (I have pinned Outlook 2016, IE, Word, Excel, Lync 2010, One Drive for Business and File Explorer).

      Any ideas?

      Reply
    23. Jonathan says:
      April 15, 2016 at 4:25 pm

      I see the WindowStyle is set hidden, but upon first login the powershell window still pops up.

      Reply
    24. Matt says:
      April 18, 2016 at 1:57 pm

      I am also experiencing the blank icons problem. Anybody have a solution yet?

      Reply
    25. Kim Nielsen says:
      April 18, 2016 at 2:47 pm

      Written by Jörgen Nilsson about 2 months ago.

      Hi,
      I will write a post on how to use it with an activesetup as soon as possible.
      /Jörgen

      Hello Jörgen. Denmark is calling 😀
      When will You do it 🙂 I’m in need of a solution to this. If I plug it in a reg file, then I’ll only get a black screem until I remove the key again. I suspect it hangs.
      I add the key like this:
      reg add “HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\Managetaskbar” /v “StubPath” /d “Powershell.exe -NoProfile -ExecutionPolicy ByPass -WindowStyle Hidden -file C:\Windows\Managetaskbar\taskband.ps1” /f

      I point it to notepad.exe and notepad opens and all hangs until I close it again, so there is something that works 🙂

      Reply
    26. Ivan Kruger says:
      April 21, 2016 at 4:21 pm

      Hi Jörgen, Please can you explain how to use this during a In-Place upgrade using ActiveSetup?

      Reply
    27. Samol says:
      April 24, 2016 at 12:00 am

      I would to thank Jörgen for the great work. For in-place upgrade please see the following blog. It looks like you have remove the last part of the powershell script.

      https://newsignature.com/articles/active-setup-windows-shell-wouldnt-start

      Credit goes to Jon Rohrich.

      Reply
      1. Zuki says:
        March 1, 2018 at 6:15 pm

        Your link has some of the worst directions I have seen. You don’t explain where ActiveSetup is in the registry, you don’t show your files, etc. You simply say “you modified Jörgen’s script to place the running of the PowerShell script into Active Setup instead of the user’s RunOnce key” with zero explanation. You need to remember that there are some people who do not know the two registry locations where ActiveSetup resides or even what it is.

        For those of you who would like more information on ActiveSetup, here is a brief summary.

        Brief Summary of Active Setup

        The purpose of Active Setup is to ensure that users have the correct settings that they need when logging on to an endpoint.

        The users’ registry captures a record of the Active Setup entries that has been run against it. In essence, the following occurs:
        1. User logs on
        2. User profile is loaded
        3. Active Setup is engaged by the logon process
        4. The following registry keys are read:
        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components; and

        HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components

        5. Compares the entries in the registry keys above to the following keys:
        HKEY_CURRENT_USER\SOFTWARE\Microsoft\Active Setup\Installed Components; and

        HKEY_CURRENT_USER \SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components

        6. If any entries are in the HKLM keys but not in HKCU then they will be processed accordingly.

        That information was borrowed from https://www.ivanti.com/blog/active-setup-and-environment-manager-personalization/

        Reply
    28. Kim Nielsen says:
      April 27, 2016 at 1:12 pm

      I made a workaround with a little help 🙂

      During WDS we run a command line “Taskbar.cmd” file.
      In this file we have this:
      reg load “hku\Default” “C:\USers\Default\NTUSER.DAT”
      reg import “%~dp0taskbar.reg”
      xcopy “%~dp0Managetaskbar” “C:\Windows\ManageTaskBar” /e /s /y /h /i
      reg unload “hku\default”
      reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run” /v “Managetaskbar” /d “C:\Windows\Managetaskbar\run.cmd” /f

      In the “run.cmd” we have this:

      IF EXIST %userprofile%\managetaskbar.txt (
      goto END ) ELSE (
      Powershell.exe -NoProfile -ExecutionPolicy ByPass -WindowStyle Hidden -file C:\Windows\Managetaskbar\taskband.ps1
      Echo %date% %time% setup done >> %userprofile%\managetaskbar.txt
      )
      :END

      Reply
    29. An says:
      April 29, 2016 at 12:23 pm

      I see the WindowStyle is set hidden, but upon first login the powershell window still pops up -> I have the same issue. Is there a solution for this?

      Reply
    30. Shane says:
      May 31, 2016 at 10:48 pm

      Brian or someone, please share how you got this working in MDT. I’m trying to do it in MDT with no luck so far.

      Reply
    31. Shane says:
      May 31, 2016 at 10:51 pm

      Can this be done in the reference image or does it have to be done at deployment time?

      Reply
    32. Geoffrey says:
      June 14, 2016 at 3:10 pm

      Also interested knowing how this is done in MDT. Can anyone share this with us?
      Thank you!

      Reply
    33. Ken Cote says:
      June 16, 2016 at 7:44 pm

      Oh man! You’re posts are just awesome! You are my new go-to guy for Windows 10 tips. Everything is so well-written, clear and accurate. I’ve used your posts for the Start Layout and now the Taskbar. Everything works, exactly as you say it. Thank you soooooo much!

      Reply
    34. Mike says:
      June 17, 2016 at 5:56 pm

      I have this working in my MDT Task Sequence after some messing around. This worked for me –

      1. Follow the guide above to get your shortcuts and registry key
      2. place Managetaskbar folder, TaskBar.cmd and Taskbar.reg into a folder
      3. Place this inside %scriptroot%
      4. Add ‘Run Command Line’ to your Task Sequence (mine is inside the Custom Tasks folder)
      5. Place path of TaskBar.cmd in Command line field e.g. %SCRIPTROOT%\MyCustomTaskbar\TaskBar.cmd
      6. Create installation media
      7. Image
      8. Beer

      One thing that I noticed the first few times I tried to get this to work was that I ended up with the correct number of blank icons in the taskbar, but these did not work as they were missing their target information.

      Sadly, I don’t have a ‘fix’ for this and I’m not sure why the shortcuts lost their information. My workflow was to copy the folder to %scriptroot%, check shortcuts’ info was intact > Create installation media (I image from a USB stick) > Mount resulting .iso, check shortcuts intact > image machine > Check result

      If you’re having trouble I would say the above is definitely worth looking at as that was my issue.

      Thanks for this awesome tip, Jörgen!

      Reply
    35. Frank says:
      June 21, 2016 at 6:59 pm

      Hi, I am little new to most of this. Can someone point me in the direction where I can learn how to create a package ? I have everything else done but I am a little confused on how to create and then deploy this package on each PC that I am configuring.

      Reply
    36. Mark Hull says:
      July 22, 2016 at 2:28 pm

      I had a problem with this not working in a domain environment on Win 10. Turns out that the issue was that the powershell that runs for each user for the first time was causing a security warning. It worked fine in a workgroup environment. There were two solutions, set the global powershell execution policy to bypass (really bad idea for security), or to add the following line to the end of the taskbar.cmd file:

      echo.>C:\Windows\ManageTaskBar\taskband.ps1:Zone.Identifier

      Hope that helps someone else. All this does is unblock the file. Jorgen, thanks for the hard work.

      Reply
    37. richb says:
      August 2, 2016 at 10:06 pm

      this worked for me on the first try in MDT!!! Thanks so much!

      Reply
    38. Kristian Fin says:
      August 5, 2016 at 2:56 pm

      Hi Jörgen,

      Nice job, but i have some problems. When iam running the .bat file local on the computer for testing i got some error when running the taskbar.bat file. reg import command says: Error: invalid syntax.

      And the xcopy command gives error Message Invalid number of parmeters.

      Hope you can help me.

      thansk.

      Reply
    39. IVAN says:
      October 11, 2016 at 11:04 am

      Hi,how to uninstall this job in win 10 anniversary update,although it not work but still have something run in backgrund

      Reply
    40. ASE says:
      October 17, 2016 at 10:28 am

      Xcopy error Message Invalid number of parmeters.

      >> Remove the “_1.0” part in the folder name

      Reply
    41. wariatos says:
      October 21, 2016 at 10:58 am

      Hi, Can anybody confirm that it work on windows 10 1511 . I run it in tasksequence in sccm but taskbar didn`t change . Powershell script run after user login and proces explorer also run. Please advice.

      Reply
    42. Jonathan Conway says:
      November 6, 2016 at 12:25 am

      I can confirm that this works fine on Windows 10 1511.

      Make sure you haven’t set the user GPO to block registry tools as that will prevent her the script from running for users when they log in.

      A workaround for this is to change the PowerShell script from using reg.exe to use “C\Windows\regedit.exe /s ” instead.

      This means you can block registry tools as long as you select the option to allow silent running in the GPO.

      Reply
    43. QWade says:
      March 20, 2017 at 9:04 pm

      I have been successful using this with clean installs, unfortunately it doesn’t set the icon customizations after an in-place upgrade moving from 7 to 10. Anyone experience this?

      Reply
    44. jf4x says:
      July 1, 2017 at 7:52 am

      Hi,

      Is this tested with W10 1703? Will it work if using custom start and taskbar layout? Current problem is that I want to remove Edge icon from taskbar.

      Reply
    45. Kevin says:
      September 8, 2017 at 6:42 pm

      not consistent with all user profiles . On same machine it worked for USER 1 and USER 2 its not working. Mean to say script is not ruined on 1st login. When I deleted the Profile it worked.. Any idea how to tackle on this issue. ?

      Reply
    46. Kafia says:
      October 3, 2017 at 9:02 pm

      I have captured an image with the all the folders included and pushed to capture wim file. Now I want edge back in the task bar, how do I delete everything without creating a new win10 1607 image file

      Reply
      1. Jörgen Nilsson says:
        October 8, 2017 at 10:48 pm

        Hi,
        Run the import command in the TS when deploying the image, if the users profile is not already created it will get the new settings.
        Regards,
        Jörgen

        Reply
    47. David says:
      October 20, 2017 at 8:49 pm

      The file structure is kind of confusing with the pictures used. I’m having a difficult time with it. if he had used this structure it would have been much easier ManageTaskbar\QuickLaunch. Can someone confirm what files go in what folder I really need this to work.

      Reply
    48. Jeff says:
      November 7, 2017 at 1:32 am

      Confirmed…”Mike’s” solution worked in MDT when nothing else did.

      Reposting Mike’s solution:

      “Mike
      I have this working in my MDT Task Sequence after some messing around. This worked for me –
      1. Follow the guide above to get your shortcuts and registry key
      2. place Managetaskbar folder, TaskBar.cmd and Taskbar.reg into a folder
      3. Place this inside %scriptroot%
      4. Add ‘Run Command Line’ to your Task Sequence (mine is inside the Custom Tasks folder)
      5. Place path of TaskBar.cmd in Command line field e.g. %SCRIPTROOT%\MyCustomTaskbar\TaskBar.cmd
      6. Create installation media
      7. Image
      8. Beer
      One thing that I noticed the first few times I tried to get this to work was that I ended up with the correct number of blank icons in the taskbar, but these did not work as they were missing their target information.
      Sadly, I don’t have a ‘fix’ for this and I’m not sure why the shortcuts lost their information. My workflow was to copy the folder to %scriptroot%, check shortcuts’ info was intact > Create installation media (I image from a USB stick) > Mount resulting .iso, check shortcuts intact > image machine > Check result
      If you’re having trouble I would say the above is definitely worth looking at as that was my issue.
      Thanks for this awesome tip, Jörgen!”

      Reply
    49. Steven says:
      March 23, 2018 at 2:55 pm

      We incorporated this with our 1511 rollout and it worked great. The only issue we have now is that users can’t remove one of these icons. It reappears after a reboot. Persists in upgrade. Anyway to completely remove one of these icons that were added?

      Reply
      1. Jörgen Nilsson says:
        April 5, 2018 at 9:05 am

        Hi,
        Yes, after 1511 you should be able to deploy a custom taskbar using the same xml as used for the Start Menu, that is how I solved it.
        Regards,
        Jörgen

        Reply
    50. Isaac says:
      May 24, 2018 at 4:44 am

      Hello,
      I set this up while on build v1709 and it worked perfectly. After updating a PC to v1803, I noticed that this Powershell script will not run when logging in as a new user. Is this a known issue?
      Thanks for all you do Jörgen.

      Reply
      1. Jörgen Nilsson says:
        June 1, 2018 at 9:39 am

        Hi,
        I haven’t tested that solution in 1803, I recommend you use the builtin feature to achieve the same https://ccmexec.com/2016/08/managing-the-taskbar-in-windows-10-using-the-new-feature-in-1607/
        Regards,
        Jörgen

        Reply
    51. Jacob Roth says:
      June 21, 2018 at 10:02 pm

      I keep getting this during the task sequence and its not working. I run the powershell script manually and it works fine. What am I missing.

      Stop-Process : Cannot find a process with the name “explorer”. Verify the process name and call the cmdlet again. RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      At C:\_SMSTaskSequence\Packages\BSP0009D\Taskband.ps1:4 char:1 RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      + Stop-Process -ProcessName explorer -Force RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      + CategoryInfo : ObjectNotFound: (explorer:String) [Stop-Process], ProcessCommandException RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      + FullyQualifiedErrorId : NoProcessFoundForGivenName,Microsoft.PowerShell.Commands.StopProcessCommand RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)
      RunPowerShellScript 6/21/2018 3:51:21 PM 3680 (0x0E60)

      Reply
    52. Pingback: Setting Internet Explorer as your default browser in Windows 10 during OS Deployment – Deployment Research
    53. Jörgen Nilsson says:
      September 4, 2020 at 12:12 pm

      Test

      Reply
    54. Pete Ghaly says:
      February 12, 2021 at 3:51 am

      Hi,

      I used this method a while ago, and it’s great. But now every time I click on the link to get the scrip it takes me to browse code samples in Microsoft website. Do you know where to get it please?

      Reply

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
    All code is provided "AS-IS" with no warranties.

    Recent Posts

    • Community tools demoed at WPNinjas 2023
    • PowerShell script to keep Personal Teams away in Windows 11
    • Windows 11 Multi-App kiosk – a first look
    • Playing around with Driver Updates in Intune
    • MMUGSE – Summer Meetup 8th of June 2023

    ©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    Non-necessary
    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
    SAVE & ACCEPT