Fantastic, that worked and I learned something new today :) "Regional settings are per user" and since ProGet runs under Network Services account, changing it simply for the current user made no difference.

Awesome support, thank you!
K>

Hi Alana,

Thanks for yours previous explanation.

I completed the migration of ProGet from one server to another in two stages.

1. I set up ProGet on a new server connecting to a cloned database and moved all Nuget and NPM packages to the same location on the new server.
2. A week later, I run a final one way sync of modified packages to the new server using a separate drop path for each package type. All packages were bulk imported and removed from the drop path so I assume it went well.

Can you see any issues arising out of migrating this way? Do you have any advice / recommendation of what to check and watch out for?

Should I still manually move modified packages as an extra precaution even I imported them via drop path? I already had one user reporting she couldn't find a package.

Thanks,

Hi,

During the migration, the ProGet article says "Copy your packages to the new server. You should copy these to the exact same directory path that the old server used."

What's the difference between the above mentioned method vs using a drop path as described by this article?

I have both, nuget and npm packages to migrate.

Regards,
K>

Fantastic, that worked and I learned something new today :) "Regional settings are per user" and since ProGet runs under Network Services account, changing it simply for the current user made no difference.

Awesome support, thank you!
K>

Hi Alana,

Yes, the server was also restarted but didn't help.

Hi Alana,

That's what I thought, but unfortunately this is not the case. I have restarted ProGet service from Windows > Servies as well as from ProGet > Administration > Manage Service > Restart Web Application.

Any other suggestion?

Thanks,
K>

Hello,

I have bulk imported lots of packages to a ProGet server via the drop-path feature when I noticed that the region of the Windows server hosting ProGet was incorrectly set to American date format MM/DD/YYYY. I have now changed this to Australian date format. DD/MM/YYYY.

As a result, when I go to Feed > NuGet >> and pick any package, the "Last Updated" field shows the incorrect date format.

Q1: Is there a simple way to change this to Australian date format for all packages?
Q2: Does it have any impact on the functionality of ProGet and how we search packages?

ProGet version 5.1.16

Thanks!
K>