reconnect network drive

I know how to connect and reconnect a network drive, but the problem is that I'm working on a corporate network where I'm just a user and my options are limited.

1. If you use the "reconnect on login", it just doesn't work. Network drive is either unavailable or gone on restart.
2. Can't use any scripts as someway they found out how to not allow you to run any CMD (or other runnable file) that is not listed in their list

I'm not trying to hack anything here, this is a stupid network drive, with stupid files, and I legally have the password to be able to connect any time I want.
But I'd like my Windows to have my drive auto-connected.
For example I can put shortcuts in the StartUp folder, but CMD files in there won't run.

How do I achieve auto-connect of this network drive ?

If you're working in an IT-managed environment, why don't you ask your IT staff for help? If your work has Active Directory, they can create a logon task to map network drives for your user account.

I don't ask because they will tell me to bugger off & come back with real problems, like the mail server is down, or something of that impact.

Can you even launch Command Prompt or PowerShell? (I doubt that it’s Not locked down - which it should be)

Try saving the mapped connection via IP instead, if you know the server’s IP

It's basic GPO work to map a network drive for a specific user account.

This is the way it works in a normal business:
1. You patiently open a request ticket. If they ignore you, wait a few days.
2. Escalate the issue to your manager. Explain how inefficiently your time is being wasted.
3. Have your manager escalate to IT. Or your manager's manager escalate to the IT manager. Front-line IT doesn't care about you. But their manager cares that a business team's manager or higher exec yelled at them.

Because IT is a cost center, and you're a profit center (hopefully).

CMD and Powershell work all right. They probably didn't lock it down because they use scripts themselves to run in the background and these risk being blocked if they block CMD/Powershell on Windows level.

I can try to setup the mapping with IP instead, didn't think of that !