How do you do your start menus.

[FN-GM]

Hi,

 

How do you do your start menus.

 

Something i dont like is global redirected and disbaled the all users folder. You end up with dead shortcuts, with my little OCD it will drive me nuts. Plus it cant go to a shared folder because of laptops going offline etc.

 

It would be nice to have everything sorted into folders. EG English, Maths etc But if you change the all users start menu and move things about and you remove applications in leaves dead links.

 

Something i am thinking about is creating a redirection to a local folder in the C drive and disable the all users folder. That way it will work offline and shortcuts to dead programs can be used. But i would like a way to hide shortcut to network applications when offline. I have found the start menu can be slow when trying to access network applications it cant get to.

 

How do you do your start menus please?

 

Thanks

Edited May 3, 2011 by FN-GM

[MicrodigitUK]

I am also looking at this for my new 2008 r2 domin and have a similar plan to you. I was going to deploy start Menue as a msi to workstations and the do a redirect to the deployed start menu. Then I was going to script some cleanup proccess that checks availability of shortcut and hides the dead links.

[glennda]

We have folders copied down on boot depending on what ou they are in (different gpo's/scripts) for Science pc's it simply copies down the folder Science and places it in the All Users Start menu. All our MSI's are then created without start-menu shortcuts and we simply put the shortcut into the folder on the network share and on next reboot they are copied down.

 

Works pretty well as is quite easy to setup.

[garethEds]

This was one of the benefits of our old RM Network - somehow the start menu knew what was installed and only built itself using those icons - no white boxes (which indeed ar a pain).

 

Cannot remember how the RM network did it though.

 

Gareth

[6Foot2]

This was one of the benefits of our old RM Network - somehow the start menu knew what was installed and only built itself using those icons - no white boxes ...

 

If anyone has the Network Manager training manuals for an RM Connect 2.4 I think there may have been an explanation as to how this works in there [if I recall correctly!]

 

I would check myself but it has been years since I managed an RM network and all of the documentation is long gone.

[AngryTechnician]

You can use Group Policy Preferences to create/delete shortcuts as needed for the user's Start Menu when they log on. I believe this is how Community Connect does it. I've found that shortcuts you set up to be created in this way are automatically skipped if the target is unavailable, so that takes care of your network availability condition.

 

Personally I have very very few programs that run from a share, but I customise almost every .msi I install to move the shortcuts into a subject folder in the All Users start menu.

[p858snake]

I've seen some people do it with folder redirections and Access-Based Enumeration to do the magic so they only get what is installed/what they are allowed but I don't have any guides handy (there should be some floating around here somewhere.

[andy_nic]

We did use start menu redirection but it lead to more problems than it solved. So we just use “all users” start menu (windows XP) and wherever windows 7 puts it now and just structure it in subject departments. Any software which points to severs runs off the intranet. We structure it to make it easier on the kids to find programs also it use to take forever to bring up the start menu when the people before my time here just left shortcuts where the programs installed them.

[FN-GM]

Thanks to those who have posted.

 

Please can more people let me know what you do?

 

Thanks

[maniac]

We use a local folder on the c:\ for start menu and desktop re-direction and a custom written startup script which only copies down the necessary icons for that machine by looking for the relevant executables on the C:\ . The Brilliant thing about this is if we distribute a piece of software we've already setup to more workstations, we don't have to mess with the start menus as the script sorts it all out for us. Works well for us and has done for the last 2 years.

 

The script could easily be modified to remove shortcuts if you un-install software as well, although I've never bothered with this as we rarely remove software from workstations once we've installed it.

 

EDIT: For dealing with un-avalable network programs I did used to use a simple VBS script 'launcher' which checked for the programs availability first, if it wasn't available then it simply gave you a message saying the program couldn't be run, but if it was then it ran it as normal. However I don't have any software which runs from network shares now so it became redundant.

Edited May 11, 2011 by maniac

[simpsonj]

Ours is in the mandatory profile, so I update it as and when new software is installed. This does lead to the occassional unsightly dead link, but I can live with it. Start menu is divided into subjects, with only accessories and Microsoft office having their own folders.

 

I think some of the above methods would be a better way to go though! Only benefit to the method I use is that its quick to setup and change, and doesn't involve running more scripts or modifying .msi files. More my limitations in that area that lead me to it I suppose.

[FN-GM]

We use a local folder on the c:\ for start menu and desktop re-direction and a custom written startup script which only copies down the necessary icons for that machine by looking for the relevant executables on the C:\ . The Brilliant thing about this is if we distribute a piece of software we've already setup to more workstations, we don't have to mess with the start menus as the script sorts it all out for us. Works well for us and has done for the last 2 years.

 

The script could easily be modified to remove shortcuts if you un-install software as well, although I've never bothered with this as we rarely remove software from workstations once we've installed it.

 

EDIT: For dealing with un-avalable network programs I did used to use a simple VBS script 'launcher' which checked for the programs availability first, if it wasn't available then it simply gave you a message saying the program couldn't be run, but if it was then it ran it as normal. However I don't have any software which runs from network shares now so it became redundant.

 

Is it possible to share the script please?

[maniac]

Is it possible to share the script please?

 

I'm not actually anywhere near my network at the moment, but if I remember when I am then I'll copy the relevant bit. It is actually already posted on here in more than one post, as people have asked me for it before. It's very simple, just 4 or 5 lines of VBS code for every program you want to distribute icons for this way, essentialy 'If EXE exists then check to see if icon's already copied and if it isn't then copy it' repeated for each program - only take seconds to run thou.

 

We also have a 'common' set of icons which gets copied to every workstation which has all the icons for things like MS office etc. and we also have another section of script which lets me distribute icons by OU - I use this when I know the same software is on every machine in an area as it's more efficient as it copies them in one block. Most of my startup script is to do with startmenu and desktop icon management.

[FN-GM]

I'm not actually anywhere near my network at the moment, but if I remember when I am then I'll copy the relevant bit. It is actually already posted on here in more than one post, as people have asked me for it before. It's very simple, just 4 or 5 lines of VBS code for every program you want to distribute icons for this way, essentialy 'If EXE exists then check to see if icon's already copied and if it isn't then copy it' repeated for each program - only take seconds to run thou.

 

We also have a 'common' set of icons which gets copied to every workstation which has all the icons for things like MS office etc. and we also have another section of script which lets me distribute icons by OU - I use this when I know the same software is on every machine in an area as it's more efficient as it copies them in one block. Most of my startup script is to do with startmenu and desktop icon management.

 

Thanks, i look forward to the script. This sounds ideal!

 

Thanks

[jcs808]

I also redirect mine to a folder on C Drive, as well as the desktop icons and wallpaper.

 

A startup script check for changes and copies then latest start menu or other changes from a network share.

 

I feel this is the best of both worlds in that the network is not hammered everytime the user clicks the start menu or logs on.

 

We do ours like Galway does.

 

This is a bit of a tangent, we have our software listed by subject. With many subjects using the same software I've been toying with the idea of listing applications by type rather than subject but I think this may be too large a step.

 

[AlexB]

I think I came up with something similar to what you are talking about...

 

I have 2 (3 if you include the staff only version) parts to this.

 

• A folder in the All Users start menu called applications that is linked to the user's start menu at login if it doesn't already exist (first login) using linkd
  
• A machine batch script that runs at boot to check 2 locations, one for creation and one for removal
  
• (A folder in the All Users start menu call staff)
  

 

The batch script has 3 variables at the top that need to be set.

cutpath is the location where the current shortcuts are

oldcutpath is where you MOVE shortcuts to after they are no longer needed

cutbase is where the script copies the shortcuts to on the local machine.

@echo off
set cutpath=\\\NETLOGON\Shortcuts
set oldcutpath=\\\NETLOGON\OldShortcuts
set cutbase=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications

for /d /r %cutpath% %%i IN (*) do (call :makefolders "%%i")

FOR /R %cutpath% %%i IN (*.lnk) DO (call :copycuts "%%i")

FOR /R %oldcutpath% %%i IN (*.lnk) DO (call :removecuts "%%i")

FOR /R %oldcutpath% %%i IN (*.remove) DO (call :removefolders "%%i")

GOTO :eof


:makefolders
set name=%1
CALL SET name=%%name:*%cutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
if not exist "%cutbase%\%name%" mkdir "%cutbase%\%name%"
goto :eof

:copycuts
set name=%1
CALL SET name=%%name:*%cutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
copy "%cutpath%\%name%" "%cutbase%\%name%" /y
goto :eof

:removecuts
set name=%1
CALL SET name=%%name:*%oldcutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
del "%cutbase%\%name%" /f /q
goto :eof

:removefolders
set name=%1
CALL SET name=%%name:*%oldcutpath%\=%%
set name=%name:~0,-9%
rem echo %name%
rmdir /s /q "%cutbase%\%name%"
goto :eof

 

Now I used the all user start menu so that when a user without lockdown/gpos logs in they still get shortcuts, but when a normal pupil or staff member logs in they don't get the all users start menu.

 

A symbolic link is used so that in windows 7 the start menu searching still works (rather than just having a shortcut that wouldn't allow windows to find programs under it)

 

To try and summarize the script it does 4 things

1. It checks for all folder at the cutpath location (including subfolders) and creates them at the cutbase location
   
2. It checks for all shortcuts at the cutpath location (including subfolders) and creates them in the same relative path at the cutbase location
   
3. It checks for all shortcuts at the oldcutpath location and removes them from the same place at the cutbase location if they exist
   
4. This last bit is a bit of a fudge, but it checks for the file ".remove" (ie no filename before the .) and if it finds at in a folder in the oldcutpath location it tries remove that folder, files and subfolders from the cutbase if it exists (obviously this should be used with care!).
   

 

What this as meant for us it that user login time is reduced, because all they do is create a symbolic link at login, and then only the first login. It does, however, increase the boot time marginally as all the shortcut management is done then.

[FN-GM]

I think I came up with something similar to what you are talking about...

 

I have 2 (3 if you include the staff only version) parts to this.

 

• A folder in the All Users start menu called applications that is linked to the user's start menu at login if it doesn't already exist (first login) using linkd
  
• A machine batch script that runs at boot to check 2 locations, one for creation and one for removal
  
• (A folder in the All Users start menu call staff)
  

 

The batch script has 3 variables at the top that need to be set.

cutpath is the location where the current shortcuts are

oldcutpath is where you MOVE shortcuts to after they are no longer needed

cutbase is where the script copies the shortcuts to on the local machine.

@echo off
set cutpath=\\\NETLOGON\Shortcuts
set oldcutpath=\\\NETLOGON\OldShortcuts
set cutbase=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications

for /d /r %cutpath% %%i IN (*) do (call :makefolders "%%i")

FOR /R %cutpath% %%i IN (*.lnk) DO (call :copycuts "%%i")

FOR /R %oldcutpath% %%i IN (*.lnk) DO (call :removecuts "%%i")

FOR /R %oldcutpath% %%i IN (*.remove) DO (call :removefolders "%%i")

GOTO :eof


:makefolders
set name=%1
CALL SET name=%%name:*%cutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
if not exist "%cutbase%\%name%" mkdir "%cutbase%\%name%"
goto :eof

:copycuts
set name=%1
CALL SET name=%%name:*%cutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
copy "%cutpath%\%name%" "%cutbase%\%name%" /y
goto :eof

:removecuts
set name=%1
CALL SET name=%%name:*%oldcutpath%\=%%
set name=%name:~0,-1%
rem echo %name%
del "%cutbase%\%name%" /f /q
goto :eof

:removefolders
set name=%1
CALL SET name=%%name:*%oldcutpath%\=%%
set name=%name:~0,-9%
rem echo %name%
rmdir /s /q "%cutbase%\%name%"
goto :eof

 

Now I used the all user start menu so that when a user without lockdown/gpos logs in they still get shortcuts, but when a normal pupil or staff member logs in they don't get the all users start menu.

 

A symbolic link is used so that in windows 7 the start menu searching still works (rather than just having a shortcut that wouldn't allow windows to find programs under it)

 

To try and summarize the script it does 4 things

1. It checks for all folder at the cutpath location (including subfolders) and creates them at the cutbase location
   
2. It checks for all shortcuts at the cutpath location (including subfolders) and creates them in the same relative path at the cutbase location
   
3. It checks for all shortcuts at the oldcutpath location and removes them from the same place at the cutbase location if they exist
   
4. This last bit is a bit of a fudge, but it checks for the file ".remove" (ie no filename before the .) and if it finds at in a folder in the oldcutpath location it tries remove that folder, files and subfolders from the cutbase if it exists (obviously this should be used with care!).
   

 

What this as meant for us it that user login time is reduced, because all they do is create a symbolic link at login, and then only the first login. It does, however, increase the boot time marginally as all the shortcut management is done then.

 

Thanks very much. What if the application isnt installed does the link still get copied down please?

 

Thanks

Edited May 11, 2011 by FN-GM
got rid of the question mark oops :-)

[AlexB]

Thanks very much? What if the application isnt installed does the link still get copied down please?

 

Thanks

 

Sorry, but no, that wouldn't work in our environment as many of the shortcuts point to mapped network drives that the local machine wouldn't see, so testing validity would cause these to drop out too.

[spc-rocket]

Hi,

 

On RM CC3 network it works by redirecting the start menu on the user's profile folder under a folder called Start Menu\Programs etc. I think there is a RM component which at logon checks to see which shortcuts have dead links to and hides them by placing a Hidden attribute. It also checks the server at a particular location X:\Group Resources\Programs which contains all the Menus for various Program sets that the user has created with the RMMC. The group resources folder also contains a text file called daserver.ini which has the name of each of the program sets followed by an = sign and then a number e.g. Core Programs=22

 

Now everytime that program set is updated or redelivered by the administration using RMMC it increments this number so when the station (or user's logon) checks this it will copy down new shortcuts or remove them depending on what has changed.

 

Its is a good method that works well on cc3 network and it is possible i guess to do on a vanilla network. Because the start menu items are cached on the user's profile most of the items are available quicker to the user (except the changes) which takes a few seconds to show sometime. This also works well because for staff laptops the start menu and program sets are also available because of the local profile being cached on their laptop.

 

Another thing RM does is that the my docs is redirected (not through a GPO but their own component) which maps it to the user's home drive and i guess this explains why we didn't any issues with adobe reader offline etc that some people have had when the used UNCs. This is easily fixed on vanilla if the in the folder redirection GPO the %homedrive% variable is used.

 

Hope this helps.

 

Ash.

[FN-GM]

Sorry, but no, that wouldn't work in our environment as many of the shortcuts point to mapped network drives that the local machine wouldn't see, so testing validity would cause these to drop out too.

 

Sorry i have missed the point. Would it copy dead short cuts for applications that are not installed?

 

Hi,

 

On RM CC3 network it works by redirecting the start menu on the user's profile folder under a folder called Start Menu\Programs etc. I think there is a RM component which at logon checks to see which shortcuts have dead links to and hides them by placing a Hidden attribute. It also checks the server at a particular location X:\Group Resources\Programs which contains all the Menus for various Program sets that the user has created with the RMMC. The group resources folder also contains a text file called daserver.ini which has the name of each of the program sets followed by an = sign and then a number e.g. Core Programs=22

 

Now everytime that program set is updated or redelivered by the administration using RMMC it increments this number so when the station (or user's logon) checks this it will copy down new shortcuts or remove them depending on what has changed.

 

Its is a good method that works well on cc3 network and it is possible i guess to do on a vanilla network. Because the start menu items are cached on the user's profile most of the items are available quicker to the user (except the changes) which takes a few seconds to show sometime. This also works well because for staff laptops the start menu and program sets are also available because of the local profile being cached on their laptop.

 

Another thing RM does is that the my docs is redirected (not through a GPO but their own component) which maps it to the user's home drive and i guess this explains why we didn't any issues with adobe reader offline etc that some people have had when the used UNCs. This is easily fixed on vanilla if the in the folder redirection GPO the %homedrive% variable is used.

 

Hope this helps.

 

Ash.

 

Sounds like what i want but its not an RM network.

[spc-rocket]

Hi,

 

I was just outlining how RM does it, i suppose there needs to be some script that runs at logon or something that check the start menu i.e if it has changed on the server and then udpate accordingly and hides the dead shortcuts by placing the the hidden attribute.

 

It should be possible to code this in VBscript or similar.

 

Ash.

[Gibbo]

Ours is in the mandatory profile, so I update it as and when new software is installed. This does lead to the occassional unsightly dead link, but I can live with it. Start menu is divided into subjects, with only accessories and Microsoft office having their own folders.

 

Same here, although I try and ensure that all apps are installed to every machine or to the network where possible to reduce the dead links.

[AlexB]

Sorry i have missed the point. Would it copy dead short cuts for applications that are not installed?

 

 

 

Sounds like what i want but its not an RM network.

 

Hi FN,

 

Yes it would copy dead shortcuts if there were any due to the previously mentioned network shortcuts. I could have 2 systems, one of network based programs and one for locally installed programs, but I haven't the need. I am wondering about a script at the end that could check through shortcuts and remove dead ones if they point to local locations that don't exist. I like the thought I might dedicate some time to it, but I have no idea if it is possible and I have my job appeal tomorrow, so it could be a while...

[AlexB]

Bah, what can I say, the idea intrigued me!

 

Anyway, this script will parse through the location defined in objStartFolder and look for any shortcuts pointing to locations beginning with sTargetStart and if they don't point to anything valid it deletes them. Afterwards it goes through and looks for empty folders and removes them too.

 

As it is set atm it looks in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications" (After first checking it exists) for any shortcuts (.lnk) that point to a target starting with "C:\" and removes it if the target doesn't exist.

 

I've hacked this together quite quickly, so don't expect anything pretty

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set oShell = CreateObject("WScript.Shell")
objStartFolder = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications"
sTargetStart = "C:\"

If objFSO.FolderExists(objStartFolder) Then

' Check for invalid shortcuts pointing to locations starting with sTargetStart
Set objFolder = objFSO.GetFolder(objStartFolder)
Set colFiles = objFolder.Files
For Each objFile in colFiles
	CheckValid objFile
Next
 
CheckSubFoldersShortcuts objFSO.GetFolder(objStartFolder)


' Check for empty folders after clearing out invalid shortcuts
CheckSubFoldersEmptyAndRemove objFSO.GetFolder(objStartFolder)

Else
'msgbox objStartFolder & " does not exist"

End If




Sub CheckSubFoldersEmptyAndRemove(Folder)
   For Each Subfolder in Folder.SubFolders
       Set objFolder = objFSO.GetFolder(Subfolder.Path)
	
	If FolderEmpty(Subfolder.Path) Then
		'msgbox "delete " & Subfolder.Path
		objFSO.DeleteFolder Subfolder.Path
	Else 
		'msgbox Subfolder.Path & " is occupied"
		CheckSubFoldersEmptyAndRemove Subfolder
	End If
   Next
End Sub


Sub CheckSubFoldersShortcuts(Folder)
   For Each Subfolder in Folder.SubFolders
       Set objFolder = objFSO.GetFolder(Subfolder.Path)
       Set colFiles = objFolder.Files
       For Each objFile in colFiles
		CheckValid objFile
       Next
       CheckSubFoldersShortcuts Subfolder
   Next
End Sub


Sub CheckValid(objCheckFile)
If LCase(objFSO.GetExtensionName(objCheckFile.name)) = "lnk" Then
	
	Set oLnk = oShell.CreateShortcut(objCheckFile.path)
	'msgbox objCheckFile.Path
	'msgbox oLnk.TargetPath
	
	If StrComp(LCase(Left(oLnk.TargetPath,Len(sTargetStart))),LCase(sTargetStart))  = 0 Then
		If objFSO.FileExists(oLnk.TargetPath) Then
			'msgbox objCheckFile.path & " is a valid shortcut"
		Else
			'msgbox objCheckFile.path & " is an invalid shortcut"
			objFSO.DeleteFile objCheckFile.path
		End If
	Else
		'msgbox "Not local shortcut"
	End If
End If

End Sub


Function FolderEmpty(strFolderPathName)
Dim oFiles, oFile, oFolder, oSubFolders, oSubFolder
Dim blnFileFound : blnFileFound = False
Set oFolder = objFSO.GetFolder(strFolderPathName)
Set oFiles = oFolder.Files
If oFiles.Count > 1 Then
	FolderEmpty = False
	Exit Function
ElseIf oFiles.Count = 1 Then
	For Each oFile In oFiles 
		If oFile.Name <> "desktop.ini" Then
			FolderEmpty = False
			Exit Function
		End If
	Next
End If
Set oSubFolders = oFolder.SubFolders
For Each oSubFolder In oSubFolders
	If Not FolderEmpty(oSubFolder.Path) Then
		FolderEmpty = False
		Exit Function
	End If
Next
FolderEmpty = True
End Function

 

I know my original script was batch, but I didn't think I could do this with batch, so vbs will have to do

[FN-GM]

Bah, what can I say, the idea intrigued me!

 

Anyway, this script will parse through the location defined in objStartFolder and look for any shortcuts pointing to locations beginning with sTargetStart and if they don't point to anything valid it deletes them. Afterwards it goes through and looks for empty folders and removes them too.

 

As it is set atm it looks in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications" (After first checking it exists) for any shortcuts (.lnk) that point to a target starting with "C:\" and removes it if the target doesn't exist.

 

I've hacked this together quite quickly, so don't expect anything pretty

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set oShell = CreateObject("WScript.Shell")
objStartFolder = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Applications"
sTargetStart = "C:\"

If objFSO.FolderExists(objStartFolder) Then

' Check for invalid shortcuts pointing to locations starting with sTargetStart
Set objFolder = objFSO.GetFolder(objStartFolder)
Set colFiles = objFolder.Files
For Each objFile in colFiles
	CheckValid objFile
Next
 
CheckSubFoldersShortcuts objFSO.GetFolder(objStartFolder)


' Check for empty folders after clearing out invalid shortcuts
CheckSubFoldersEmptyAndRemove objFSO.GetFolder(objStartFolder)

Else
'msgbox objStartFolder & " does not exist"

End If




Sub CheckSubFoldersEmptyAndRemove(Folder)
   For Each Subfolder in Folder.SubFolders
       Set objFolder = objFSO.GetFolder(Subfolder.Path)
	
	If FolderEmpty(Subfolder.Path) Then
		'msgbox "delete " & Subfolder.Path
		objFSO.DeleteFolder Subfolder.Path
	Else 
		'msgbox Subfolder.Path & " is occupied"
		CheckSubFoldersEmptyAndRemove Subfolder
	End If
   Next
End Sub


Sub CheckSubFoldersShortcuts(Folder)
   For Each Subfolder in Folder.SubFolders
       Set objFolder = objFSO.GetFolder(Subfolder.Path)
       Set colFiles = objFolder.Files
       For Each objFile in colFiles
		CheckValid objFile
       Next
       CheckSubFoldersShortcuts Subfolder
   Next
End Sub


Sub CheckValid(objCheckFile)
If LCase(objFSO.GetExtensionName(objCheckFile.name)) = "lnk" Then
	
	Set oLnk = oShell.CreateShortcut(objCheckFile.path)
	'msgbox objCheckFile.Path
	'msgbox oLnk.TargetPath
	
	If StrComp(LCase(Left(oLnk.TargetPath,Len(sTargetStart))),LCase(sTargetStart))  = 0 Then
		If objFSO.FileExists(oLnk.TargetPath) Then
			'msgbox objCheckFile.path & " is a valid shortcut"
		Else
			'msgbox objCheckFile.path & " is an invalid shortcut"
			objFSO.DeleteFile objCheckFile.path
		End If
	Else
		'msgbox "Not local shortcut"
	End If
End If

End Sub


Function FolderEmpty(strFolderPathName)
Dim oFiles, oFile, oFolder, oSubFolders, oSubFolder
Dim blnFileFound : blnFileFound = False
Set oFolder = objFSO.GetFolder(strFolderPathName)
Set oFiles = oFolder.Files
If oFiles.Count > 1 Then
	FolderEmpty = False
	Exit Function
ElseIf oFiles.Count = 1 Then
	For Each oFile In oFiles 
		If oFile.Name <> "desktop.ini" Then
			FolderEmpty = False
			Exit Function
		End If
	Next
End If
Set oSubFolders = oFolder.SubFolders
For Each oSubFolder In oSubFolders
	If Not FolderEmpty(oSubFolder.Path) Then
		FolderEmpty = False
		Exit Function
	End If
Next
FolderEmpty = True
End Function

 

I know my original script was batch, but I didn't think I could do this with batch, so vbs will have to do

 

Thanks, does this work with the Batch File or instead of please?